Resume management and recruitment workflow system and method

ABSTRACT

A computer system and method for managing access to a resume database. For each skill or experience-related phrase in a resume, the system computes a term of experience based on an experience range associated with a contextual use of the phrase in the resume. The term of experience for a phrase that occurs multiple times in the resume is the summation of the term of experience for each occurrence of the phrase associated with a different contextual use. The system stores each phrase and the term of experience in a parsed resume. The resume database also stores job descriptions that include required phrases and a required term of experience for each required phrase. The job descriptions also store a required level of education or field of specialization, and a required salary range. A recruiter searches the resume database to find matching resumes that satisfy a job description.

This application is a continuation of U.S. patent application Ser. No. 14/089,464 filed Nov. 25, 2013, which is a continuation of U.S. patent application Ser. No. 12/726,253 filed Mar. 17, 2010, now U.S. Pat. No. 8,595,149, which is a Division of U.S. patent application Ser. No. 10/418,142 filed Apr. 18, 2003, now U.S. Pat. No. 7,711,573. The entire disclosure of each of the priority applications is incorporated herein by reference.

FIELD OF THE INVENTION

The present invention relates, in general, to computing systems and data processing. In particular, the present invention is a computer system and method for managing access to a resume database, searching the resume database, generating a resume summary based on a stored resume and job description, accessing a resume management and recruitment workflow system via a graphical user interface, and composing a resume for a candidate.

BACKGROUND OF THE INVENTION

When an employer decides to hire a new employee, a hiring manager determines requirements for the new employee. The requirements include mandatory characteristics for the new employee. With the requirements in mind, the hiring manager begins to review resumes that the employer receives from potential candidates.

A resume, or curriculum vitae, summarizes a candidate's career and qualifications. The resume is a mechanism to convey personal and business-related characteristics that the candidate believes to be relevant to a prospective employer. The resume typically includes the candidate's career objective, personal interests, professional affiliations, educational background, employment history, and a description of work experience.

Reviewing candidate resumes is typically a manual process that involves the hiring manager reading or scanning each paper or electronic resume in a stack of resumes with the requirements for the new employee in mind. After reading or scanning a resume, the hiring manager decides whether the candidate's qualifications described in the resume can possibly satisfy the job requirements. For each resume that seems to satisfy the requirements, the hiring manager contacts the potential candidate and attempts to schedule an interview. Once the potential candidate accepts the invitation to interview, the potential candidate becomes a candidate for the new position. One disadvantage of this process is the time required by the hiring manager to review resumes that do not possibly qualify for the position. The hiring manager is reviewing a large number of resumes for the purpose of narrowing them down to a few resumes that describe candidates who might qualify for the position and warrant an interview or hire. Furthermore, the accuracy of the process depends on the accuracy of the hiring manager who is reading or scanning the large number of resumes. Thus, the manual process does not lend itself to reviewing a large enough number of resumes and is likely to miss the resume of a qualified potential candidate or find the resume of an unqualified potential candidate.

Prior electronic systems improved upon the manual process by creating a database of resumes and tools to search the database. The impetus for developing these systems was to reduce the time required to review resumes, eliminate the tediousness of the task, and improve the accuracy of the search. These prior systems typically scanned a database of documents using a textual word search of the resume content. The textual word search did not account for alternative terminology, spelling, format, or case differences between the search terms and the resume content. The textual word search also did not take into account the length of the duration of an experience. Since these prior systems rely upon key words to describe the resume content, the disadvantages of these prior systems are similar to those of the manual process. These prior systems retrieve a much larger number of resumes than the number of possibly qualified resumes. Thus, these systems retrieve a large number of irrelevant resumes. To narrow the output to a short list, these systems require a further manual review tallying the maximum possible duration of experience for each required skill or experience-related phrase. This manual review is still timely and prone to error. Borrowing a term from the science and art of data mining, the precision ratio of prior systems has been extremely low. For certain technical jobs and jobs that require more than minimal experience, the precision ratio can be under 5% and at times even below 1%.

Other prior electronic systems attempted to solve the reduction of the large number of resumes to a short list of possibly qualified candidates by ignoring the resume and relying upon the candidate to input the duration of experience that they have in a skill or experience-related phrase. A search performed by these systems include the duration of experience on only a predetermined set of skill or experience-related phrases and rely on the candidate or the candidate's representative to correctly enter the duration of experience for the skill or experience-related phrase. These systems may consider alternate terminology, spelling, or formatting differences, but only for the predetermined set of skill or experience-related phrases. There are three principal disadvantages to these systems.

First, prior electronic systems provide a very time consuming set-up for candidates or their representatives. The candidate must enter each acquired skill or experience-related phrase and the associated duration of experience. This becomes a particularly daunting task when considering the number of recruitment systems to which an applicant might want to post a resume or list of qualifications. It is also a daunting task for the recruitment systems managers because their staff must read each resume or interview each candidate to obtain as many skill or experience-related phrases as possible from their previous experiences.

Second, prior electronic systems are not dynamic. They cannot consider a skill or experience-related phrase and its possible duration of experience as soon as the resume arrives into the system. In these systems, a new skill or experience-related phrase will never be searchable for a given duration of experience unless the users of the system grant the skill or experience-related phrase the status of being searchable by duration of experience, irrespective of the existence of the resume in the system.

Third, prior electronic systems tally the duration of experience for a skill or experience-related phrase at search time by utilizing traditional search techniques. Performing the tallying of years of experience at search time optimizes storage and data normalization and provides a simple traditional construct to the SELECT statement of a relational database. Unfortunately, tallying the duration at search time is a processor intensive operation that negatively impacts the system performance.

Thus, there is a need for a resume management and recruitment workflow system that includes search and recruitment workflow tools to reduce a resume database to a manageable number of resumes by identifying a set of candidates who can possibly satisfy the qualifications and requirements sought by a hiring manager. The search should identify any resume that includes the sought after qualification or requirement and should also interpret synonymous or alternative terms to be equivalent to the sought after qualification or requirement. Furthermore, the search should identify most resumes that can possibly include the sought after qualification or requirement and should avoid identifying resumes that cannot possibly include the sought after qualification or requirement. The qualifications and requirements should include any skill or experience-related phrase that appears in a resume, but should also accommodate requiring a candidate to possess the qualification or requirement for a specified minimum period of time. The present invention addresses this need.

SUMMARY OF THE INVENTION

A computer system, method, and computer program product for managing access to a resume database. The method comprises receiving a resume that includes at least one skill or experience-related phrase, storing the resume in the resume database, computing a term of experience for each skill or experience-related phrase, and storing a parsed resume in the resume database. The parsed resume includes each skill or experience-related phrase, the term of experience, and a relationship between the term of experience and each skill or experience-related phrase. The resume further includes a contextual use for each skill or experience-related phrase, the contextual use having an experience range. The term of experience for each skill or experience-related phrase being derived from the experience range of the associated contextual use. When the experience range is zero, the term of experience is set to zero. When the experience range is greater than zero, the term of experience is the time difference between the start time and the end time of the experience range rounded down to a unit of time, such as a number of seconds, minutes, hours, days, weeks, months, years, or decades. For each skill or experience-related phrase that is a repeated entry, the computation of the term of experience is the sum of the time difference for each repeated entry that is in a different experience range.

The storing of the parsed resume further comprises storing each skill or experience-related phrase having an identical term of experience as an element defined by a markup language (e.g., XML), the element comprising a start tag, content data, and an end tag. The start tag and the end tag include the identical term of experience, and the content data includes each skill or experience-related phrase having the identical term of experience. In another embodiment, the content data further includes a nested element comprising a nested start tag, nested content data, and a nested end tag. The nested start tag and the nested end tag include a nested term of experience, and the nested content data includes each skill or experience-related phrase having the nested term of experience. In another embodiment, the nested term of experience is greater than the identical term of experience.

In another embodiment, the method further comprises receiving a job description, storing the job description in the resume database, sending a database query to the resume database, receiving a result set in response to the database query, and sending a portion of the result set. The job description including at least one job requirement, where each job requirement includes a required skill or experience-related phrase and a required term of experience. The result set includes at least one matching resume from the resume database with each matching resume satisfying the job description. The required term of experience is rounded up to a unit of time, such as a number of seconds, minutes, hours, days, weeks, months, years, or decades. In another embodiment, the job description further includes a required level of education or a required field of specialization. In another embodiment, the job description includes a required salary range comprising a minimum required salary and a maximum required salary.

In another embodiment, the method comprises associating at least one of the skill or experience-related phrases with at least one implied skill or experience-related phrase, storing searchable phrases in the parsed resume, and computing a term of experience for each of the searchable phrases. The searchable phrases include the skill or experience-related phrases and each implied skill or experience-related phrase. To associate skill or experience-related phrases with implied skill or experience-related phrases, the method retrieves each implied skill or experience-related phrase from a mapping table that relates skill or experience-related phrases to implied skill or experience-related phrases. The term of experience for each searchable phrase is derived from the experience range of the contextual use associated with the searchable phrase.

In another embodiment, the method comprises receiving a request to search the resume database, receiving search criteria, sending a database query to the resume database, receiving a result set in response to a database query, and sending the result set in response to the request. In another embodiment, the method comprises sending a request to search the resume database, sending search criteria, and receiving a result set in response to a database query to the resume database. The result set including at least one matching resume from the resume database, where each matching resume satisfies the search criteria.

In another embodiment, the method comprises receiving a request to generate a summary of a resume, selecting a job description, sending a database query to the resume database, receiving a result set in response to the database query, and storing the resume summary. The result set including the resume and the resume summary, where the resume summary includes the required skill or experience-related phrases.

In another embodiment, a graphical user interface comprises a first data entry region, a second data entry region, and a search button. The first data entry region includes at least one required skill set, where each required skill set comprises a required skill or experience-related phrase and a required term of experience. The second data entry region includes a search string comprising at least one search phrase, where each search phrase includes one of the required skill sets and a one-to-one mapping exists between the search phrases and the required skill sets. The search button being operative to send to a resume database, a database query that includes the search string.

In another embodiment, the system updates the search string in the second data entry region to reflect changes made by a user editing the required skill sets in the first data entry region. Similarly, the processor also updates the required skill sets in the first data entry region to reflect changes made by a user editing the search string in the second data entry region.

In another embodiment, the method comprises sending scripted questions to a candidate, receiving responses to the scripted questions, and composing grammatically correct sentences based on the responses. The responses describe a job history for each job held by the candidate.

The preceding summary of the invention is presented to assist with understanding the invention and is neither an exhaustive nor an exclusive summary. It should be understood that this summary of the invention is not representative of all of the inventions defined by the claims, to be considered limitations on the invention as defined by the claims, or limitations on equivalents to the claims. Thus, this summary of the invention should not be considered dispositive when determining equivalence. Additional features and advantages of the invention will become apparent from a review of the detailed description, figures, and claims.

FEATURES AND ADVANTAGES

The resume management and recruitment workflow system allows a candidate to store requisite experiences, capabilities, and competencies by merely posting their electronic or digital resume to the system. The candidate does not need to complete forms and assign years of experience to a predefined set of skill or experience-related phrases. The system retains all of the experiences, skills, and experience-related phrases for the candidate and assigns the maximum possible duration of experience for each utilizing this information for the employer to execute a search with great accuracy, i.e., an improved precision ratio.

The resume management and recruitment workflow system allows a hiring manager or recruiting representative to search a resume database for a candidate having a specific skill or experience-related phrase at a required minimum duration of experience. This search allows the hiring manager or recruiting representative to reduce a large pool of resumes to a short list of resumes and to obtain a short list of candidates. The candidates in this short list will have the required skill or experience-related phrases at possibly the required duration of experience as long as the resume contains job narratives that contain the skill or experience-related phrase, and the duration of the various jobs held by the candidate. The search user interface allows the hiring manager or recruiting representative to draft a database query using either an intuitive interface or a Boolean phrase interface. The system converts the one form of data entry to the other and vice-versa.

From each posted resume, the system extracts each skill or experience-related phrase and stores it in an XML file within a duration tag. The duration tag has a value that is smaller than the maximum possible duration of experience of the skill or the experience-related phrase but is the largest value among the values of elements of a pre-established series of duration tags. Future searches for a candidate relies on the experience-related phrases and associated duration tag stored in a resume database for retrieval by the hiring manager of possibly suitable candidates. The system does not require real-time tallying of duration of experience for skill or experience-related phrases at search time.

The system stores in the XML file the creation date of the resume in a number of different time units. The user will be able to retrieve resumes for a period of time whose length is any one of these time units and whose creation date is so many such time units from a pre-determined date. In the Gregorian calendar system, Dec. 12, 2003 is 2003 years from 1 A.D., 24,036 months from January, 1 A.D. and approximately 731,596 days from 12:00 A.M. January 1, 1 A.D. For storing the creation or arrival date of a resume, this system created a different calendar system whose units are not necessarily days, months and years. This system enables the recruiter to retrieve all resumes that have arrived within any of such units of time on any past date. For instance, if a three-days unit is one such unit of time, then this system can retrieve three days worth of resumes that meet a certain criteria on a specified date that is so many multiples of three days from the pre-determined date. So, although this system will be retrieving data that is created between two dates that are three days apart, the stored date in the XML file will be a unique number identifying each of the three days. Similar to the Gregorian calendar, which utilizes days, months and years as units of time, this system utilizes a number of time units, which are pre-determined by the implementers of the system. Optimizing the data retrieval to the user's liking influences the determination of the length and number of these time units. Smaller number of time units tends to cause the units to carry high values and will cause the system to retrieve a larger number of resumes. However, if you need to narrow the number of resume retrieved, then a large number of such units is established, where the units' values will be narrowly spread out.

The system stores the salary in multiples of a predetermined series of values. For instance, an 82,000 U.S. dollar salary is four 20,000 U.S. dollar units, sixteen 5,000 U.S. dollar units and eighty-two 1,000 U.S. dollar units. This system retrieves all resumes whose desired salaries fall in a range whose length is one such dollar unit. All resumes in this dollar range, whose length is the value of the dollar unit, carry the same attribute or multiple of that unit. Retrieving all resumes with a certain value of the multiple will retrieve resumes whose desired salary is with a range whose length is one such dollar unit amount. This system can retrieve resumes within a dollar range without having to execute data base retrieval statements that utilize the greater, smaller or between operators.

The system stores educational information, which includes degree, field of specialization, school name, and year of graduation. This system allows the user to filter or retrieve resumes based on criteria related to education. Degrees are nested in a hierarchy. For instance, a resume of a candidate who holds a master degree will appear in nested enclosures for an associate, bachelor, and master degrees. The implementation can be made to accommodate any number of degrees that run in a hierarchy. Two degrees belong to the hierarchy when one implies the other. For instance, the holder of a Master's degree either holds a Bachelor's degree or has the qualifications of at least the holder of a Bachelor's degree.

The system maps each skill or experience-related phrase to a number of broad terms or phrases when a candidate posts the resume to the system. The system stores the broad terms or phrases and their maximum possible duration of experience in the same fashion as it does for the narrow terms or phrases, from which the broad terms or phrases were derived. Thus, the search will have a direct hit for requested skill or experience-related phrases as well as direct hits for their broad terms or experience-related phrases. Note that a broad term or phrase is a term or a phrase that is implied by another term or phrase. The latter term or phrase is the narrow term of the broad term that it implied. The term ‘imply’ is the Aristotelian implication in Logic as in the statement: “If A then B”. In this statement A implies B. Therefore, B is a broad term of A and A is a narrow term of B.

After locating each skill or experience-related phrase, the system displays the data extrapolated from the resume to the candidate and allows the candidate to correct, add, or delete any information from the resume. In another embodiment, the system assists the candidate with developing a resume by asking the candidate a series of questions designed in such a way that the answers will make up the phrases and sentences that comprise the content of a job assignment description. In another embodiment, when a hiring manager's search identifies a suitable candidate, the system will generate for each employer's job, a summary of the candidate's background that highlights the experiences most pertinent to the job requirements.

The preceding features and advantages are presented to assist with understanding the invention and are neither an exhaustive nor an exclusive summary. It should be understood that these features and advantages are not representative of all of the inventions defined by the claims, to be considered limitations on the invention as defined by the claims, or limitations on equivalents to the claims. Thus, these features and advantages should not be considered dispositive when determining equivalence. Additional features and advantages of the invention will become apparent from a review of the detailed description, figures, and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying figures best illustrate the details of the resume management and recruitment workflow system and method, both as to its structure and operation. Like reference numbers and designations in these figures refer to like elements.

FIG. 1 is a block diagram that illustrates the integration of resume management and recruitment workflow system 140 into an operating environment for a traditional job-opening fulfillment or employment-seeking situation, in accordance with one embodiment of the present invention.

FIG. 2 is a network diagram that illustrates exemplary input and output hardware components that may form the operating platform for resume management and recruitment workflow system 140 shown in FIG. 1, in accordance with one embodiment of the present invention.

FIG. 3 is a block diagram that illustrates the hardware and software components comprising resume management and recruitment workflow system 140 shown in FIG. 2, in accordance with one embodiment of the present invention.

FIG. 4 illustrates the conversion of an exemplary paper resume into an exemplary XML resume, in accordance with one embodiment of the present invention.

FIG. 5 is an exemplary database structure for resume database 302 shown in FIG. 3, in accordance with one embodiment of the present invention.

FIG. 6 is a flow diagram of an embodiment of resume management and recruitment workflow system 140 receiving a job requirement from recruiter 120 a or adding a resume from candidate 110 a.

FIG. 7 is a flow diagram of an embodiment of resume management and recruitment workflow system 140 displaying a list of jobs, searching through previously entered and stored job descriptions and their specifications, and adding a new job and its description and specification.

FIG. 8 is a flow diagram of an embodiment of resume management and recruitment workflow system 140 parsing resume 115 a, storing its parsed data in resume database 302 and matching resume 115 a and its candidate 110 a to a stored job, if applicable.

FIG. 9 is a flow diagram of an embodiment of resume management and recruitment workflow system 140 searching resume database 302 for a list of resumes and, therefore, candidates that meet a set of requirements input by recruiter 120 a.

FIG. 10 is a data flow diagram of an embodiment of resume management and recruitment workflow system 140 illustrating an exemplary job search.

FIG. 11 is a data flow diagram of an embodiment of resume management and recruitment workflow system 140 illustrating the transmission of a resume from candidate 110 a to resume database 302.

FIGS. 12A through 12M are exemplary screen images from an implementation of resume management and recruitment workflow system 140.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 is a block diagram that illustrates the integration of resume management and recruitment workflow system 140 into an operating environment for a traditional job-opening fulfillment or employment-seeking situation. In one embodiment, candidate 110 a authors resume 115 a in an electronic format and stores resume 115 a in resume management and recruitment workflow system 140 as a public resume. The phrase “public resume” indicates that the system stores the resume and allows any buyer (e.g., recruiter 120 a) to access the resume without restriction. The electronic format includes any standard digital document format comprising text file formats such as American Standard Code for Information Interchange (ASCII) or Extended Binary Coded Data Interchange Code (EBCDIC), word processor file formats such as Microsoft Word or WordPerfect, and markup language file formats such as Standard Generalized Markup Language (SGML), HyperText Markup Language (HTML), or eXtensible Markup Language (XML). Recruiter 120 a determines a set of requirements and searches resume management and recruitment workflow system 140 for any resume that matches the set of requirements. Each requirement includes at least one required skill or experience-related phrase and a required minimum duration of experience associated with the skill or experience-related phrase. The phrase “matches the set of requirements” indicates that the resume includes each experience-related phrase in the set of requirements and that the maximum possible duration of experience for each experience-related phrase exceeds the required minimum duration of experience defined by hiring manager 130 a. In another embodiment, the phrase “matches the set of requirements” indicates that the resume includes additional criteria (e.g., education, salary range, or geographic location) as defined by hiring manager 130 a. If resume 115 a matches the set of requirements, recruiter 120 a retrieves a copy of resume 115 a, optionally reviews the resume or interviews the candidate as an additional screening step, and sends it to hiring manager 130 a for review. Even though this embodiment only illustrates the interaction of candidate 110 a, recruiter 120 a, and hiring manager 130 a, it is to be understood that resume management and recruitment workflow system 140 can accommodate any number of candidates, recruiters, and hiring managers.

FIG. 1 also illustrates another embodiment that integrates recruitment team 125 into resume management and recruitment workflow system 140. Recruitment team 125, as shown in FIG. 1, includes recruiter 120 b and recruiter 120 c however, it is to be understood that recruitment team 125 may include any number of recruiters. Candidate 110 b, candidate 110 c, and candidate 110 d each agreed to work with recruitment team 125. Candidate 110 b, candidate 110 c, and candidate 110 d author, respectively, resume 115 b, resume 115 c, and resume 115 d in an electronic format and store resume 115 b, resume 115 c, and resume 115 d in resume management and recruitment workflow system 140 as private resumes. The phrase “private resume” indicating that the system stores the resume and restricts access to the resume to the members of a specific group of system users. As shown in FIG. 1, the specific group is recruitment team 125. As shown in FIG. 1, candidate 110 b previously authored another instance of resume 115 b and stored the other instance of resume 115 b in resume management and recruitment workflow system 140 as a public resume. Thus, resume 115 b is a “semi-private resume” because the other instance of resume 115 b discloses to the public the information common to both the public and private instance of resume 115 b. In another embodiment, the private resume is a replacement for the public resume. The recruiters comprising recruitment team 125 have access to both public and private resumes and search resume management and recruitment workflow system 140 for any resume that matches the set of requirements defined by hiring manager 130 a and another set of requirements defined by hiring manager 130 b. If resume 115 c matches the set of requirements defined by hiring manager 130 b, a member of recruitment team 125 retrieves a copy of resume 115 c, optionally reviews the resume or interviews the candidate as an additional screening step, and sends it to hiring manager 130 b for review. Even though this embodiment only illustrates the interaction of candidate 110 b, candidate 110 c, candidate 110 d, recruitment team 125, hiring manager 130 a, and hiring manager 130 b, it is to be understood that resume management and recruitment workflow system 140 can accommodate any number of candidates, recruiters, and hiring managers.

FIG. 2 is a network diagram that illustrates exemplary input and output hardware components that may form the operating platform for resume management and recruitment workflow system 140 shown in FIG. 1. Network 200, as shown in FIG. 2, is a public communication network that connects and enables data transfer between the input hardware components, output hardware components, and resume management and recruitment workflow system 140.

Network 200 shown in FIG. 2 is a public communication network however, resume management and recruitment workflow system 140 contemplates the use of comparable network architectures. Comparable network architectures include the Public Switched Telephone Network (PSTN), a public packet-switched network carrying data and voice packets, a wireless network, and a private network. A wireless network includes a cellular network (e.g., a Time Division Multiple Access (TDMA) or Code Division Multiple Access (CDMA) network), a satellite network, and a wireless Local Area Network (LAN) (e.g., a wireless fidelity (Wi-Fi) network). A private network includes a LAN, a Personal Area Network (PAN) such as a Bluetooth network, a wireless LAN, a Virtual Private Network (VPN), an intranet, or an extranet. An intranet is a private communication network that provides an organization, such as a corporation, with a secure means for trusted members of the organization to access the resources on the organization's network. In contrast, an extranet is a private communication network that provides an organization, such as a corporation, with a secure means for the organization to authorize non-members of the organization to access certain resources on the organization's network. The system also contemplates network architectures and protocols such as Ethernet, Token Ring, Systems Network Architecture, Internet Protocol, Transmission Control Protocol, User Datagram Protocol, Asynchronous Transfer Mode, and proprietary network protocols comparable to the Internet Protocol.

The input hardware components shown in FIG. 2 include client computer 210, personal digital assistant (PDA) 212, mobile device 214, server computer 216, and comparable devices. Client computer 210 is a general-purpose personal computer, workstation, or laptop configured to connect to network 200. PDA 212 is a portable handheld device, such as a Palm handheld or Microsoft Pocket PC, configured to connect to network 200 either directly or via client computer 210. When PDA 212 disconnects from client computer 210, PDA 212 operates upon downloaded data stored locally until reestablishing the connection to client computer 210 and synchronizing the data. Mobile device 214 is a portable wireless device that connects to resume management and recruitment workflow system 140 via network 200. In another embodiment, mobile device 214 is a land-based or wireless telephone that connects to resume management and recruitment workflow system 140 via network 200. Server computer 216 is a general-purpose network computer that manages network resources and accepts connections from computers such as client computer 210 via network 200. It is to be understood that the input hardware components shown in FIG. 2 are illustrative examples that demonstrate the functions performed by a component and are not intended to limit resume management and recruitment workflow system 140.

In one embodiment, candidate 110 a operates the input hardware components shown in FIG. 2 to create and store resume 115 a in an electronic format. After storing resume 115 a, candidate 110 a operates the input hardware component to access resume management and recruitment workflow system 140 via network 200 and sends resume 115 a to resume management and recruitment workflow system 140. In another embodiment, candidate 110 a operates the input hardware component to access resume management and recruitment workflow system 140 and relies upon programmed instructions residing in resume management and recruitment workflow system 140 to create resume 115 a and store the resume on resume management and recruitment workflow system 140. In another embodiment, candidate 110 a operates the input hardware component to access resume management and recruitment workflow system 140 via network 200 and verify or update the content of resume 115 a that was previously transmitted to resume management and recruitment workflow system 140. In another embodiment, candidate 110 a operates the input hardware component to access resume management and recruitment workflow system 140 and verify or update the data parsed from candidate resume 115 a. In another embodiment, candidate 110 a operates the input hardware component to access resume management and recruitment workflow system 140 and search a database of job descriptions stored by recruiters such as recruiter 120 a. In another embodiment, candidate 110 a operates the input hardware component to access resume management and recruitment workflow system 140 and submit resume 115 a for a job description stored by a recruiter such as recruiter 120 a. In one embodiment, the input hardware component performs a resume “bulk load” by accessing resume management and recruitment workflow system 140 via network 200 to transmit at least one resume using a transmission protocol such as the file transfer protocol (FTP). In another embodiment, the resume bulk load is an automatic, scheduled process that occurs periodically.

The output hardware components shown in FIG. 2 include client computer 220, PDA 222, mobile device 224, server computer 226, and comparable devices. Client computer 220 is a general-purpose personal computer, workstation, or laptop configured to connect to network 200. PDA 222 is a portable handheld device, such as a Palm handheld or Microsoft Pocket PC, configured to connect to network 200 either directly or via client computer 220. When PDA 222 disconnects from client computer 220, PDA 222 operates upon downloaded data stored locally until reestablishing the connection to client computer 220 and synchronizing the data. Mobile device 224 is a portable wireless device that connects to resume management and recruitment workflow system 140 via network 200. In another embodiment, mobile device 224 is a land-based or wireless telephone that connects to resume management and recruitment workflow system 140 via network 200. Server computer 226 is a general-purpose network computer that manages network resources and accepts connections from computers such as client computer 220 via network 200. It is to be understood that the output hardware components shown in FIG. 2 are illustrative examples that demonstrate the functions performed by a component and are not intended to limit resume management and recruitment workflow system 140.

In one embodiment, recruiter 120 a operates the output hardware component shown in FIG. 2 to access resume management and recruitment workflow system 140 via network 200 and relies upon programmed instructions residing in resume management and recruitment workflow system 140 to create a job that includes at least one requirement. Each requirement includes a skill or experience-related phrase that a candidate 110 a must possess and a minimum duration of time that the candidate 110 a could have possibly practiced the skill or experience-related phrase. Typically, a skill or experience-related phrase will appear in a resume in a context that implies a maximum duration of time that the candidate 110 a has practiced the skill or experience-related phrase (i.e., the duration of time is non-negligible). This mention of the experience-related phrase might also occur when candidate 110 a has studied the subject matter represented by the experience-related phrase. Although the phrase might not belong to a job with a duration of experience, the experience-related phrase might also be mentioned in resume 115 a when candidate 110 a is familiar with the phrase, had read about it, or other reasons that deemed candidate 110 a to include it. If the context does not imply a duration of time (i.e., the duration of time is zero) or implies a duration of time that is less than one time unit (i.e., the duration of time is negligible), the maximum duration of time associated with the skill or experience-related phrase will be set to zero. Thus, the skill or experience-related phrase will be attributed to the resume. However, the weight attributed to the skill or experience-related phrase will be negligible. Situations that will cause the maximum duration of time to be zero include candidate 110 a attending a class or seminar on a particular subject matter, or being familiar with a subject matter, but having no formal experience with the subject matter. After creating a job, recruiter 120 a operates the output hardware component to access resume management and recruitment workflow system 140 via network 200 and verify the status of a job that was previously created and stored in resume management and recruitment workflow system 140. In another embodiment, resume management and recruitment workflow system 140 automatically searches its database for any resume such as resume 115 a that matches the job requirement and displays resume 115 a and the contact information for candidate 110 a on client computer 220 for recruiter 120 a. Resume 115 a is a match if it contains a skill or experience-related phrase in the job requirements and if the duration of experience derived from the context of the skill or experience-related phrase exceeds the maximum duration of time associated with the skill or experience-related phrase in the job requirements. The phrase “maximum-total-duration” refers to the maximum possible duration of time that candidate 110 a can take credit for a skill or experience-related phrase that appears in resume 115 a. XML table 540 only stores a portion of the maximum-total-duration because the actual maximum-total-duration of each experience-related phrase extracted from resume 115 a is rounded to the closest smaller duration tag in XML table 540. Thus, the maximum-total-duration for a skill or experience-related phrase is the summation, over every job experience range in resume 115 a, of the duration of time for the skill or experience-related phrase. In another embodiment, recruiter 120 a searches resume management and recruitment workflow system 140 to locate matching candidates. Candidate 110 a is a match for a job if resume 115 a includes each skill or experience-related phrase, or the associated narrow phrases, that comprise the requirements for the job and where, for each skill or experience-related phrase, the rounded maximum-total-duration of experience exceeds the required minimum duration of time. In one embodiment, the output hardware component performs a job “bulk load” by accessing resume management and recruitment workflow system 140 via network 200 to transmit at least one job using a transmission protocol such as the file transfer protocol (FTP). In another embodiment, the job bulk load is an automatic, scheduled process that occurs periodically.

FIG. 3 is a block diagram that illustrates the hardware and software components comprising resume management and recruitment workflow system 140 shown in FIG. 2. Resume management and recruitment workflow system 140 is a general-purpose computer. Bus 300 is a communication medium that connects central processing unit (CPU) 301, resume database 302, data storage 303, and network adapter 304 to memory 305. Network adapter 304 also connects to network 200 and is the mechanism that facilitates the passage of network traffic between resume management and recruitment workflow system 140 and network 200. CPU 301 performs the disclosed methods by executing the sequences of operational instructions that comprise each computer program resident in, or operative on, memory 305.

FIG. 3 illustrates resume database 302 and data storage 303 as separate devices however, it is to be understood that another embodiment is to store the data in a single physical device that includes a separate logical partition for resume database 302 and data storage 303. FIG. 3 also illustrates resume database 302 and data storage 303 as internal devices however, it is to be understood that in another embodiment these devices may each be external to resume management and recruitment workflow system 140 and accessible via a network connection. Resume management and recruitment workflow system 140 also contemplates distributing resume database 302 over multiple storage devices to suit efficiency, performance, backup, and data warehousing requirements. In one embodiment, resume database 302 utilizes a relational database management system such as Oracle 9i (version 9.2) by Oracle™. Another embodiment of resume database 302 may utilize a different database management tool that is either homegrown or publicly available and traded. Another embodiment of resume database 302 may utilize an object-oriented database management system such as FrameD, open source software provided by SourceForge.net.

In one embodiment, the configuration of memory 305 includes user interface program 310, search data entry program 311, resume parser program 312, phrase mapping program 313, job creation program 314, resume searching program 315, resume generator program 316, and resume maker program 317. These computer programs store intermediate results in memory 305 and transmit final results via bus 300 for storage in resume database 302 or data storage 303. It is to be understood that in another embodiment the configuration of memory 305 may not simultaneously include these programs. CPU 301 coordinates loading a program when it is needed, storing intermediate results, transferring data from one program to another, and unloading the program when it is no longer needed.

User Interface Program

User interface program 310 is a web-based graphical user interface such as a hypertext markup language (HTML) web page that is accessible using a general-purpose hypertext transfer protocol (HTTP) web browser such as Netscape Communicator, Microsoft Internet Explorer, or Mosaic. In another embodiment, user interface program 310 is a standalone application program implemented using an interface tool such as Java, or Microsoft Visual Basic. A user, such as candidate 110 a or recruiter 120 a, operates user interface program 310 to access search data entry program 311, resume parser program 312, phrase mapping program 313, job creation program 314, resume searching program 315, resume generator program 316, and resume maker program 317. A connection pool management program such as the OC4j (version 1.0) portion of Oracle 9i manages the connections between the user interface program 310 and the programs comprising resume management and recruitment workflow system 140. A description of these programs follows in the discussion of the flowcharts shown in FIGS. 6, 7, 8, and 9. In another embodiment, a different set of software and hardware tools can service the connection and communication between the user or the user interface on one hand and the programs listed in memory 305 of resume management and recruitment workflow system 140 on the other hand.

Search Data Entry Program

Search data entry program 311 is the tool that recruiter 120 a uses to compose the criteria for searching resume database 302 to identify resume 115 a as possibly satisfying the requirements for a job and identifying candidate 110 a as a possible match for the job. Candidate 110 a is a matching candidate if the resume of candidate 110 a contains the set of requirements whose rounded-down maximum possible duration of experience that is derived from the resume exceeds the rounded-up required minimum duration of experience for each of the skill or experience-related phrases required by the job and defined in the composed criteria. Again, this maximum possible duration as known to the searchable XML table 540 is the rounded figure, which is referred to in this disclosure as the rounded-maximum-total-duration of experience. Search data entry program 311 permits recruiter 120 a to enter the criteria as a Boolean phrase of skill or experience-related phrases very similar to the data entry for search engines found in prior electronic systems. Search data entry program 311 converts the Boolean phrase into an intuitive layout of a list of required skill or experience-related phrases and possible alternative skill or experience-related phrases. In another embodiment, search data entry program 311 permits recruiter 120 a to enter the criteria as the list of required skill or experience-related phrases and possible alternative skill or experience-related phrases. Search data entry program 311 then converts the intuitive layout of a list of required skill or experience-related phrases and possible alternative skill or experience-related phrases to a Boolean phrase. The data entered in Search data entry program 311 is the input to resume searching program 315.

Search data entry program 311 will replay itself for the user allowing the user to possibly enter another criteria, which will be utilized to remove candidates from the list of candidates who fit the previously entered criteria. In other words, search data entry program 311 accepts mandatory criteria to which the qualifications of the resulting resumes have to adhere and optional similarly laid-out criteria to which the qualifications of the resulting resumes cannot adhere. A resume adhering to the second criteria will be taken out of the list of resumes that adhere to the firstly entered criteria.

In another embodiment, search data entry program 311 accommodates educational requirements in its search criteria. Recruiter 120 a can specify the required level of education and field of specialization.

In another embodiment, search data entry program 311 accommodates salary requirements in its search criteria. Recruiter 120 a can specify a range of required salaries.

Resume Parser Program

An input to resume parser program 312 is resume 115 a in an electronic format. Suitable transmission means for carrying resume 115 a in an electronic format include an electronic mail message, an uploaded file, a “cut and paste” block of text, and output from a program such as resume maker program 317. A transmission means such as an electronic mail message will include resume 115 a in an electronic format as an attachment. A transmission means such as an uploaded file comprises resume 115 a in an electronic format that resume parser program 312 receives via a protocol such as FTP. A transmission means such as “cut and paste” cuts from one location, or program running on a general-purpose computer, a block of text comprising resume 115 a and pastes the block of text into a resume input associated with user interface program 310. A transmission means such as resume maker program 317 is a specifically designed transmission means.

After receiving resume 115 a, resume parser program 312 parses the resume to extract certain attributes of the candidate and all experience-related phrases and the maximum-total-duration of experience for each phrase. The attributes include the candidate's name, residence or business address, telephone numbers (e.g., home, work, facsimile, and cellular), e-mail addresses, education data (e.g., degree, major, year, and school name), past employer data (e.g., employer name, last title, and period of employment), and salary (e.g., current and expected).

During the parsing of resume 115 a, resume parser program 312 identifies the beginning and end of the experience portion of resume 115 a. The beginning of the experience portion occurs when the word “experience,” or a synonymous word or phrase, appears as a heading in resume 115 a. In another embodiment, the beginning of the experience portion occurs at the start of resume 115 a. The experience portion of resume 115 a by-passes narratives on education, objective, references, hobbies, summary of skills, name, address, phone numbers, electronic mail address, awards, non-experience related achievements, non-experience related accomplishments, and other narratives that do not define experience over a specified duration of time. The end of the experience portion occurs either when resume parser program 312 reaches the end of the resume or when a heading appears such as education, references, hobbies, or other headings that are not related to a job experience.

Resume parser program 312 extracts a start-date and an end-date from the description of each employer or job assignment in the experience portion of resume 115 a. A job assignment description is all the text that starts with the line that includes the start-date and ends at the line before the line that includes the next start-date. In another embodiment, a job assignment description in resume 115 a ends at the end of resume 115 a or one line before the appearance of a non-experience-related heading like references, education or hobbies in resume 115 a. The duration of experience, the term of experience, or the experience range, is the duration of time resulting from the subtraction of the end-date for a job assignment description from the start-date for the job assignment description. The start-date and end-date for a job assignment description in resume 115 a appear on one line with a separator in between. The separator can be a space, a character, or a term or a phrase that means “to” (e.g., “10/1/99 to 11/24/01” or “Oct. 1, 1999-11/24/2001”). In another embodiment, the start-date, separator, and end-date of a job assignment description in resume 115 a appear on two or three consecutive lines respectively. When only two lines are used the separator might be a null, implied by a carriage-return or line-feed, a hidden or unprintable character, or non-existent. The maximum duration for any skill or experience-related phrase that appears in the description of that employer or job assignment is the duration of time between the start-date and the end-date. If the start-date or the end-date are not present in the description, then resume parser program 312 sends an electronic message to candidate 110 a requesting that candidate 110 a edit resume 115 a to include date ranges for each of the job assignment descriptions via user interface program 310. In another embodiment, after receiving the electronic message sent by resume parser program 312, candidate 110 a can edit resume 115 a on client computer 210 and retransmit resume 115 a to resume management and recruitment workflow system 140.

Resume parser program 312 also extracts each phrase contained in every job assignment description portion of resume 115 a. A phrase is a sequence of one or more consecutive words. A word is a sequence of one or more consecutive printable characters, numbers, or symbols. Extracted phrases from a job assignment description in resume 115 a can have overlapping words or overlapping sub-phrases. For example, if the phrase “Utilized Java and Oracle” appears in a job assignment description of resume 115 a, the extracted phrases include “Utilized”, “Java”, “and”, “Oracle”, “Utilized Java”, “Java and”, “and Oracle”, “Utilized Java and”, “Java and Oracle”, and “Utilized Java and Oracle”. Each extracted phrase from a job assignment description is a “skill or experience-related phrase” and includes one or more consecutive words in the description of the employer or job assignment. Each experience-related phrase is stored in resume database 302 and is associated with a maximum possible duration of time (e.g., number of months, or number of years) that candidate 110 a possessed the experience-related phrase. An experience-related phrase includes or describes a skill, job location, title, department, responsibility, duty, action, achievement, accomplishment, relationship, product, consultation, group, team, field, space, area of endeavor, company, industry, technical package, or tool.

When resume parser program 312 finishes parsing resume 115 a, resume parser program 312 sends an electronic mail message to candidate 110 a that includes a link to the parsed resume. Candidate 110 a reviews the candidate attributes and the job experiences with their start-dates and end-dates as parsed by resume parser program 312 and is able to revise any information that is incorrect. In one embodiment, candidate 110 a sends the revised copy as a replacement resume.

Phrase Mapping Program

Phrase mapping program 313 maps all experience-related phrases to their possible synonyms and to their broad terms or broad phrases. An experience-related phrase includes, but is not limited to skills that are utilized on the job, all functions that are performed on the job, and all other terms, acronyms, or phrases used in the job assignment description. The information and narratives in the job assignment description comprise statements or phrases that includes one or more words or terms where a word or a term includes one or more characters, numbers, or symbols. Additionally, the word or the term would be preceded and trailed by a delimiter such as a space or non-alphanumeric character. Phrase mapping program 313 maps individual words and consecutive words (i.e., statements or phrases) to their possible synonyms and broad terms in the English language. A broad term or phrase is a term or a phrase that another term or phrase implies (i.e., a broad phrase is an implied phrase). For instance, “human” is a broad term for “soldier”, “banker” is a broad term for “lending officer”, and “medical doctor” is a broad term for “psychiatrist” or “neurologist”. Since “medical doctor” is a synonym for “physician”, the phrase “medical doctor” is a broad phrase for “physician” and “physician” is a broad term for “medical doctor”. The phrase “speaks Spanish very well” is a synonym for the phrase “fluent in Spanish” and therefore, both phrases are broader than each other. However, “fluent in Spanish” is a broad term for “Spanish author”. Phrase A is a narrow term or phrase (i.e., a narrow phrase is an implying phrase) of phrase B when phrase B is a broad phrase of phrase A.

Phrase mapping program 313 is activated to map newly introduced mappings to mapping table 530. Every time resume management and recruitment workflow system 140 adds a map of a phrase to another phrase in mapping table 530, resume management and recruitment workflow system 140 looks up in resume database 302 all the resumes containing the narrow phrase. Resume management and recruitment workflow system 140 utilizes the new mapping to introduce the broad phrase to all the corresponding records in XML table 540. Note that, resume management and recruitment workflow system 140 will attempt to avoid duplication. If a job experience contains the phrase “Java”, and its newly mapped narrow phrase “JSP”, resume management and recruitment workflow system 140 will not add to the maximum-total-duration of “Java” any duration contributed to by the existence of “JSP” in the mentioned job. Conversely, if “Java” is not explicitly listed in the job assignment description, the introduction of a mapping making “JSP” a narrow phrase of “Java”, will cause the resume management and recruitment workflow system 140 to add the duration of experience of the job containing “JSP” to the maximum-total-duration of “Java”.

The job assignment description or experience portion of a resume begins on the line that includes the start-date of a date range (e.g., “10/1/99 to 11/24/01” or “10/1/99-11/24/01”) and ends one line before the line that includes the next start-date, if any. The resume management and recruitment workflow system 140 will parse numerous layouts of date ranges including those that might appear on one, two or three lines. Date ranges would initiate job experiences once the program determines that they belong within the experience portion of the resume. The verbiage of a job assignment description may also end when headings on non-job related matters appear. Such headings may include education, references, and hobbies.

During the parsing of resume 115 a, resume management and recruitment workflow system 140 gives skill or experience-related phrases in a job assignment description their due weight, in units of time representing the maximum possible duration of experience. As mentioned above, experience-related phrases in a job assignment description can range from one to any number of consecutive words. The duration between the start-date and the end-date in the date range, which defined and started the job assignment description (or experience), is an attribute assigned to each of the experience-related phrases, mentioned above, along with their synonyms and broad phrases. For each experience-related phrase in a single resume, the length of time associated with each appearance of the experience-related phrase in a job experience is tallied to compute a total duration for the experience-related phrase, its synonyms, or broad phrases for the whole resume. By definition and inference, this total duration for each phrase represents the total duration of experience the owner of the resume could have had in the phrase describing, for example, a skill, job location, title, department, responsibility, duty, action, achievement, accomplishment, relationship, product, consultation, group, team, field, space, area of endeavor, company, industry, technical package, or tool. In other words, the total duration of all the jobs, for each experience-related phrase appearing in resume 115 a of candidate 110 a, is the maximum duration of experience candidate 110 a could have had in the experience-related phrase. This maximum duration of experience is referred in this disclosure as the maximum-total-duration.

As previously defined, the term as “maximum-total-duration” for each experience-related phrase refers to the maximum duration per experience-related phrase per resume, and therefore, per candidate. The “total” is for the possible multiplicity of jobs or experiences, in which the experience-related phrase appears, in resume 115 a. The duration is at its possible maximum because resume 115 a and resume parser program 312 provided all the possible experiences that contain the experience-related phrase. Additionally, during an individual job, candidate 110 a could have used an experience-related phrase contained in resume 115 a for at most the total duration of the job that contains the phrase. The total of all the duration of all the jobs that contain the experience-related phrase is the maximum-total-duration of experience in the phrase for candidate 110 a.

The maximum-total-duration can be in any duration of time such as a number of seconds, minutes, hours, days, weeks, months, years, or decades. Resume management and recruitment workflow system 140 indexes the experience-related phrase in an Extensible Markup Language (XML) table within a duration tag, that represents the largest duration tag among a series of duration tags that is smaller than the maximum-total-duration of the experience-related phrase resulting from resume 115 a. In one embodiment, the series of duration tags is chosen so as to optimize the search for candidates, the matching of candidates to jobs, and to get the narrowest possible results without missing any significant number of resumes. For further discussion on the elements in the series of the duration tags, please refer to the section in this disclosure on XML table 540. For example, if resume 115 a includes a first job lasting 24 months and a second job lasting 36 months, each experience-related phrase in resume 115 a will have a maximum-total-duration attribute with a value of 24, 36, or 60 months depending on whether the experience-related phrase appears in the first job, the second job, or both jobs. Any experience-related phrase that appears in resume 115 a has only one value for its maximum-total-duration attribute.

When resume management and recruitment workflow system 140 receives resume 115 a, the experience-related phrases are mapped to their broad phrases. For candidate search and job-to-candidate matching purposes, the newly derived broad phrases become new experience-related phrases in the job assignment description that contains the original experience-related phrase from which the broad phrase was derived. By recursion, this mapping and implication process is repeated until the entire original and derived experience-related phrases have been mapped to all their possible and available broad phrases. This mapping process refers to mapping table 530 as the thesaurus for implication to broad phrases. Since concatenating newly derived broad experience-related phrases does not occur within the job experience, neither a partial phrase of the newly generated experience-related phrases nor a concatenation of a number of the newly generated experience-related phrases with each other, with the original experience-related phrases, or with parts thereof generate any newer experience-related phrases. After all the mappings are completed, the maximum-total-duration of experience for each experience-related phrase, original and new, is tallied. The tallying of the maximum-total-duration of experience does not differentiate between an original skill or experience-related phrase that appeared verbatim in the original resume and a derived broad phrase that came about as a broad phrase through implication by the thesaurus mapping table 530.

Note that a broad experience-related phrase might not have existed in the job that contained the original narrower experience-related phrase, from which it was derived, but it might exist in another job that does not contain the original narrower experience-related phrase. It is therefore deduced that while the maximum-total-duration of the original narrow experience-related phrase might only be the length of the job that contains the narrow experience-related phrase, the maximum-total-duration of the broad phrase will be the total duration of both jobs. In other words, the maximum-total-duration of a broad experience-related phrase is at least, but can be more than, the maximum-total-duration of the narrow phrase that implied it. The mapping process, the tallying process of maximum-total-duration, and the storing and indexing of the experience related phrases in XML table 540 are performed when the resume is received by resume management and recruitment workflow system 140. Resume searching program 315 fetches preprocessed and already indexed data.

Job Creation Program

Job creation program 314 enables recruiter 120 a to utilize user interface program 310 to enter data that describes a job and the requirements that a potential candidate should possess to be a match for the entered job. Job creation program 314 stores the entered data in job table 520. In another embodiment, before storing the entered data, job creation program 314 activates resume searching program 315 to locate potential candidates whose resume is a match to the entered job. In another embodiment, when resume 115 a arrives, the system examines the resume to determine whether it matches any job entered by recruiter 120 a and stored in job table 520. If resume 115 a matches a job stored in job table 520, resume management and workflow system 140 automatically alerts recruiter 120 a, the creator of the job, of the arrival of resume 115 a. Recruiter 120 a can review resume 115 a and send it to hiring manager 130 a or flag resume 115 a for future reference. In another embodiment, after reviewing resume 115 a, recruiter 120 a does not send resume 115 a to hiring manager 130 a and does not flag resume 115 a for future reference.

In another embodiment, job creation program 314 allows recruiter 120 a to clone a job. Recruiter 120 a will be able to enter or create a job similar to an existing job upon the click of a button. The cloning will create a new job with the same specifications, required criteria, and hiring manager 130 a of the cloned job. The new job will have the cloning date for the creation date and will not share notes and job activities with the original job.

Resume Searching Program

Resume searching program 315 searches resume management and recruitment workflow system 140 for the resumes that meet input criteria. Resume 115 a meets the input criteria if the rounded-up required duration of each required experience-related phrase or its stated alternative in the job criteria is less than the maximum-total-duration tag of the experience-related phrase or its alternative in resume 115 a. This excludes those phrases specified by the excluding criteria where the excluding criteria is laid out similar to the required including criteria.

For example, resume 115 a includes four jobs with a respective duration of 10, 20, 60, and 60 months. Using every combination of the four jobs, the only possible values for maximum-total-duration of experience (i.e., term of experience) of any experience-related phrase are 60, 60, 120, 20, 80, 80, 140, 10, 70, 70, 130, 30, 90, 90, and 150 months. If the duration tags are monthly, the XML tags that may include skill or experience-related phrases, are <S060>, <S060>, <S120>, <S020>, <S080>, <S080>, <S140>, <S010>, <S070>, <S070>, <S130>, <S030>, <S090>, <S090>, and <S150>. After eliminating duplicate tags, the only possible XML tags that may include skill or experience-related phrases are <S010>, <S020>, <S030>, <S060>, <S070>, <S080>, <S090>, <S120>, <S130>, <S140>, and <S150>. When indexing, the nesting of the possible values of the maximum-total-duration tags is in ascending order. Between these tags, there are monthly tags that contain no skill or experience-related phrases. It is to be understood that the outer tags implicitly contain the skill or experience-related phrases contained in any of the inner higher valued tags. The maximum-total-duration tag or attribute becomes a key. The resume identifier, the maximum-total-duration tag and the skill or experience-related phrase, to which it is an attribute, make up a virtual composite key to the XML table. In another embodiment, when XML is not utilized, the resume identifier, the experience-related phrase, and each period less than or equal to the maximum-total-duration tag make up a composite key to an indexed table that points to resume table 550.

In the criteria, resume searching program 315 allows for substitution of an alternative for a required experience-related phrase. For resume 115 a to be a match, the maximum-total-duration tag for the alternative in resume 115 a should be greater than or equal to the rounded-up required duration in the criteria of resume searching program 315.

In addition, resume searching program 315 implicitly allows for the substitution of a narrow skill or experience-related phrase of a required experience-related phrase for the required experience-related phrase if the narrow experience-related phrase's maximum-total-duration tag in resume 115 a is greater than or equal to the rounded-up required duration of the required broader experience-related phrase. This substitution is implicit because it does not take place at search time. Again, the substitution was accomplished when resume 115 a was received by resume management and recruitment workflow system 140 and the broad phrase was derived as an experience-related phrase wherever its narrow phrases existed as experience-related phrases. Upon receipt of resume 115 a, phrase mapping program 313 of resume management and recruitment workflow system 140 has already included the broad phrase as an experience-related phrase in the index. The maximum-total-duration tag of this broad newly generated experience-related phrase is at least the maximum-total-duration tag of the narrow experience-related phrase from which it was implied. Therefore, once the maximum-total-duration tag of the newly derived broad experience-related phrase is more than its rounded-up required duration by the search, resume 115 a becomes a match to the job or search requirement. Although the original resume 115 a did not contain the phrase in the search criteria, the developed index of experience-related phrases for resume 115 a does contain the phrase and when the maximum-total-duration tag is greater than or equal to the rounded-up required duration, resume 115 a becomes a match.

According to one embodiment of the system, the “SELECT” statement of a search will identify a candidate with 80 months of experience in an experience-related phrase even if the search requires fewer months of experience (e.g., 65 months) in the experience-related phrase. Additionally, an experience-related phrase associated with a duration of 70 months of experience will have its own nest and will not appear in the 80 months nest or in the outer nests that represent 60, 30, 20, and 10 months. Since the nesting includes every possible duration that the job experiences of a resume can provide, each experience-related phrase of a resume will belong to one and only one nest. In a series of monthly nests, there will be additional nests to the ones mentioned above for each month from one up to the highest number of months less than or equal the largest maximum-total-duration attribute among the maximum-total-duration attributes of the experience-related phrases in resume 115 a.

In another embodiment, resume searching program 315 accommodates educational requirements in its search criteria. Candidate 110 a will satisfy the required educational level when the highest degree that is earned by candidate 110 a is higher than the required educational level. The field of specialization is met when the degree for candidate 110 a satisfies the degree level requirement and is in the required field of specialization or in a narrower field that implies the required field of specialization as per mapping table 530. For example, candidate 110 a satisfies a requirement for a bachelor degree in biology when candidate 110 a holds a Ph.D. in genetics.

In another embodiment resume searching program 315 accommodates salary requirements in its criteria. Resume searching program 315 selects a salary range unit for searching based upon the difference between the maximum and minimum salary for the required salary range. For example, a salary range unit can be a 20,000-dollar, 5,000-dollar, or 1,000-dollar unit. If the search is for an individual whose salary is between 250,000 and 300,000 dollars, then the 20,000-dollar unit range will be searched on first. Resume searching program 315 will search for multiples of 13, 14 and 15 of the 20,000-dollar range. If a 12, but not 13 or higher, multiple of the 20,000-dollar range is found then, a 50 or 51 multiple of the 5,000-dollar range should be present for candidate 110 a to fit the criteria. If a 13, 14 or 15 multiple are found of the 20,000-dollar range then candidate 110 a meets the salary requirement criteria.

Resume searching program 315 performs a search and displays the result of the search via user interface program 310. The search results include a job applicant's resume and the candidate attributes. User interface program 310 displays candidates in a split screen format with the attributes of a selected candidate from the list on one side of the screen and the candidate resume on the other side of the screen. The default display presents the latest copy of the candidate's incoming resume however, a user such as recruiter 120 a may also choose to view other resumes for the same candidate, if available. The user may also choose to display the attributes and resumes of other candidates from the output list. The user may also scroll up and down the list selecting the next and previous candidates on the list or directly jumping to a candidate on the list without scrolling.

For individual candidates, the candidate attributes, the candidate activities, the candidate notes, a copy of one of the candidate resumes, and the results of the search will simultaneously remain displayed on the screen while recruiter 120 a is flipping from one resume of the candidate to another. User interface program 310 displays the same corresponding information for each new candidate selected from the output list. The user is only limited by the size of the display screen when adjusting how much of the resume, candidate attributes, candidate activities, and output of the search shows on the screen.

A candidate having more than one resume stored in resume table 550 of resume database 302 will have different records in XML table 540 corresponding to each resume. For the candidate to be a match to the requirements of a job or to a search, only one resume needs to match the job requirements or the search criteria. The candidate will appear once on the list of matched candidates.

Resume Generator Program

Resume generator program 316 uses the job data entered by job creation program 314 and resume 115 a to generate a new version of resume 115 a for candidate 110 a. In one embodiment, resume 115 a is a match to the job requirements. In another embodiment, resume 115 a is not necessarily a match to the entered job. For example, resume 115 a may not include a phrase specified in the job requirements, but does include a narrower phrase or a broader phrase for the phrase specified in the job requirements. In both cases, resume generator program 316 produces a new resume that highlights the skill or experience-related phrases required by the entered job and summarizes the job's requirements that are found in resume 115 a.

Resume generator program 316 produces a resume summary that includes the total duration of work experience of candidate 110 a, the duration of experience that candidate 110 a possess in each skill or experience-related phrase required by the job, the duration of experience that candidate 110 a possess in each of the phrases that are stated in the job requirements as alternates to the required experience-related phrases, and the duration of experience that candidate 110 a possess in the narrow phrases of both the required skill or experience-related phrases and their alternates. Educational background of candidate 110 a and the original summary from resume 115 a are also included in the newly produced summary. The summary also includes prior job titles for candidates 110 a. The summary will also contain the duration of each of the job titles. Resume generator program 316 makes use of the output of resume parser program 312 to derive the total duration of work experience and the duration of experience in each of the required experience-related phrases, their alternatives, and the narrow phrases of both. Additionally, resume generator program 316 makes use of the output of resume parser program 312 to arrive at the educational background of candidate 110 a and the job titles that candidate 110 a has held. The generated summary includes statements from existing summaries in the original resume. The newly generated resume contains all the experiences found in the original resume. In the newly generated resume, resume generator program 316 highlights (e.g., changes the text appearance to a bold font style) the experience-related phrases that are required by the job; the alternative phrases, which are stated in the job requirement, of the required experience-related phrases; and the narrow phrases of both the required experience-related phrases and the alternatives that are referred to herein. The newly generated resume will only contain information derived from, extrapolated from, or implied by the contents of resume 115 a.

Resume Maker Program

Resume maker program 317 enables candidate 110 a to make resume 115 a. Prior electronic systems and resume management and recruitment workflow system 140 provide the capability that enables candidate 110 a to enter their name, address, home phone number, work phone number, facsimile number, cellular telephone number, electronic mail address, earned degrees, field of specialization, the name of educational institutions attended, graduation years, expected salary, and job history. Prior electronic systems and resume management and recruitment workflow system 140 allow candidate 110 a to chronologically enter a job history for each prior employer. The job history includes a start and end date for the employment, titles held by candidate 110 a, a description of the functions, responsibilities, and duties performed by candidate 110 a or an organization to which candidate 110 a belongs, accomplishments attributed to candidate 110 a, and tools that candidate 110 a used during the employment. Some prior electronic systems provide tool tips in the form of samples of resumes, text from existing resumes, or instructions on the expected content of the description of the performed function. However, resume maker program 317 is unique because it composes the description of the performed function for each of the jobs held by candidate 110 a. A series of scripted questions that are part of resume maker program 317 are administered to candidate 110 a. The mentioned scripted questions comprise multiple choice questions, questions that can only be answered with a yes or a no, and questions that can only be answered with a word, a phrase, a list of words, or a list of phrases. Resume maker program 317 then composes full sentences from the answers to the scripted questions and makes up the description of the performed function. Resume maker program 317 asks candidate 110 a a subset of the totality of questions that it contains. In order to compose the description of the performed function, resume maker program 317 dynamically chooses which questions to ask based on the answers to previously asked questions. For example, resume maker program 317 asks candidate 110 a for their title at a job. If the response from candidate 110 a is “programmer”, then resume maker program 317 will ask which programming languages he used. However, if the response from candidate 110 a is “manager”, then resume maker program 317 will ask how many people he supervised. Resume maker program 317 asks candidate 110 a to state their individual responsibility, the responsibility of each person they supervised, the department they worked in, and the company that they worked for. Resume maker program 317 asks candidate 110 a to state the hierarchy of the organizations that he worked for and their titles (e.g., department, division, group, etc.). Resume maker program 317 asks candidate 110 a for the names of the tools, processes, machinery, or systems that he used. Resume maker program 317 also asks candidate 110 a for the names of the tools, processes, machinery, systems, services, products, or duties he produced or performed. Resume maker program 317 then composes full sentences out of the responses of candidate 110 a to the questions asked by resume maker program 317. The resulting narrative is then presented to candidate 110 a for proof-reading and editing. No further questioning is then performed.

FIG. 4 illustrates the conversion of an exemplary paper resume into an exemplary XML resume. Paper resume 400 includes summary narrative 401, experience narrative 402, and closing narrative 403. Summary narrative 401 includes resume headings and their content such as the executive summary, career objective, education, professional summary, and professional certifications. Experience narrative 402 includes the employer or job assignment descriptions that comprise the work experience heading of the resume or a synonymous heading. Closing narrative 403 includes resume headings and their content such as hobbies, security clearance, references, or technical skills. Resume management and recruitment workflow system 140 converts paper resume 400 into XML resume 410. Lines 2-40 of XML resume 410 represent the conversion of paper resume 400. Lines 3-17 of XML resume 410 represent administrative sections that identify the recruitment team ID, salary requirement, and creation date of XML resume 410. Lines 18-39 of XML resume 410 define the experience-related phrases and education data parsed from the paper resume 400. The <Work Experience> tag comprises a series of nested <S_> tags. Each <S_> tag defines the experience-related phrases that correspond to a given duration of experience, i.e., term of experience. Thus, <S000> defines the experience-related phrases that appear in paper resume 400, but correspond to a duration of time from zero to less than the duration of the next nested <S_> tag. For example, the <S000> tag contains any skill or experience-related phrase that occurs in summary narrative 401 or closing narrative 403, but not in experience narrative 402. <S003> defines the experience-related phrases that correspond to at least three months of maximum-total-duration of experience up-to the next <S_> tag. Note that any skill or experience-related phrase that occurs in experience narrative 402 is associated with a maximum-total-duration of three or more months. Further, <S006> defines those three or more months experience-related phrases that correspond to six or more months of maximum-total-duration of experience (i.e., any experience-related phrase that occurs in experience narrative 402 and is associated with a maximum duration of six or more months). Thus, the skill or experience-related phrases are stored in nested tags and, when the experience-related phrase is indexed under the tag, the skill or experience-related phrase, the corresponding duration tag and the resume identifier become a composite key to XML table 540. Furthermore, the resume identifier, the maximum-total-duration, and the associated experience-related phrase comprise a virtual composite key to XML table 540. The example of XML resume 410 shown in FIG. 4 includes a tag series where the first two elements represent three months and six months. Also, XML resume 410 represents a candidate whose total experience is more than six months but less than the duration represented by the next or third series tag that is higher than six months. Candidate 110 a whose resume 115 a generated XML resume 410 does not have experience beyond or more than the third tag in the series. Therefore, the third and higher tags do not need to appear in XML resume 410. XML resume 410 will include enough <S_> tags to span the entire duration of experience in the resume. For example, if a resume has two jobs, one lasting 24 months and the other lasting 36 months, then the last internal nested <S_> tag will be <SXXX> where XXX is the highest valued tag, which is smaller or equal to 60 months. Regardless whether there are corresponding experiences, all the <S_> series elements up to the highest tag are inserted in the XML resume 410. Among them are the tags, which are the highest tags smaller or equal to each of the 24, 36 and 60 months correspondingly.

In one embodiment, the database management tool uses XML to index and store the experience-related phrases and their maximum-total-duration of experience. In another embodiment, a different database tool may employ another tool to store the same information and make it rapidly accessible at search time.

In another embodiment, an experience-related phrase and the highest tag series element that is smaller than the maximum-total-duration of the experience-related phrase can be used as an indexed composite key to a table that points to resume 115 a. Additionally, for each such composite key, more composite keys are generated from the experience-related phrase and each of the elements in the series that are less than or equal to the maximum-total-duration. All of these keys would be indexed in a table that points to resume 115 a in resume table 550. For example, for a tag series with data elements using a number system in months (i.e. one month, two months, three months, etc.). If candidate 110 a has resume 115 a that contains the phrase “Java” at a maximum-total-duration of eight months, then eight composite keys will be generated, each containing “Java” at one, two, three, four, five, six, seven, and eight months consecutively. A search or a job description that requires a minimum of five and a half months of experience will retrieve the record containing the composite key of “Java” and six months via a direct hit. Again, no tallying of years of experience at search time will be required. Additionally, “Java” could have been either an original experience-related phrase or a derived one via an implication that utilized an original narrower phrase and mapping table 530.

FIG. 5 is an exemplary database structure for resume database 302 shown in FIG. 3. Resume database 302 comprises candidate table 510, job table 520, mapping table 530, XML table 540, and resume table 550. In another embodiment, the system distributes the tables that comprise resume database 302 among several computers configured similarly to resume management and recruitment workflow system 140. In another embodiment, resume database 302 also includes tables containing candidate activities and notes, job activities and notes, recruiter table and level of authorization, recruiter activities and notes, as well as joining tables to optimize the storage and performance of the system for an ideal normalization level. The distributed architecture will improve load balancing by distributing the processing required to populate, search, maintain, and backup the database.

Candidate Table

Candidate table 510 stores information related to each candidate such as data extracted from the candidate's resume, data entered by the candidate or an administrator on behalf of the candidate and notes and recruitment activities entered by recruiter 120 a, pertaining to the candidate. The data extracted from the candidate's resume and the data entered by the candidate or an administrator on behalf of the candidate include personal identification and contact information, work experience data, job assignment descriptions, education credentials, job skills, and other experience-related phrases. The notes input by the recruiter include a synopsis of conversations between the candidate and the recruiter, the candidate's interview schedule, and the candidate's availability status.

Job Table

Job table 520 stores information related to each job or position that a hiring manager needs to fill such as requirements for a job and notes relating to candidates for the job. Job table 520 includes the employer or hiring manager identification and contact information, the recruiter identification information, if different from the employer or hiring manager, the requirements for the job, and the notes and recruitment activities pertaining to the job. The requirements for the job include the work location, the duration of the job assignment, and the pay scale. The requirements for the job also include required skill or experience-related phrases and their alternatives, and the required minimum duration of experience for each required skill or experience-related phrase, and the required minimum duration of experience for each stated alternative of each skill or experience-related phrase. The requirements for the job allow for the exclusion of candidates, who fit criteria similar to the criteria specified herein as the required candidate's inclusion criteria. Other inclusion and exclusion conditions may include geographic locations (states), area codes, salary ranges, and educational levels. The notes relating to candidates for the job include a synopsis of conversations between the candidate, the recruiter, and the hiring manager, as well as a list of the interviewees for the job.

Mapping Table

Mapping table 530 retains the broad and narrow phrases of phrases encountered by resume parser program 312. A definition of “phrase” includes one or more consecutive words. Phrase A is broad phrase of phrase B when phrase B implies phrase A. Likewise, phrase B is a narrow phrase of phrase A when phrase B implies phrase A. Phrase A and phrase B are synonymous when phrase A is a narrow and broad phrase of phrase B and vice versa. A detailed discussion of mappings in this system is in the disclosure of phrase mapping program 313. Mapping table 530 attempts to include any phrase that might appear in a resume and that might have possible broad and narrow phrases. Mapping table 530 is utilized by phrase mapping program 313 as a thesaurus of phrases implying other phrases. Mapping tables 530 also includes the exceptions when a supposedly broad or narrow phrase is not broad or narrow because of context. For instance, experience in ‘bank’ does not imply ‘banking’ experience when ‘bank’ appears in the resume in the context of ‘data bank’.

XML Table

XML table 540 retains the rows of XML resume 410 and points to resume table 550, which contains resume 115 a, in a one-to-one correspondence between XML resume 410 of XML table 540 and resume 115 a of resume table 550. Resume parser program 312 and phrase mapping program 313 convert resume 115 a of candidate 110 a into the exemplary rows comprising XML resume 410 as shown in FIG. 4. For each resume, there is a resume identifying tag followed by extracted attributes from resume 115 a for candidate 110 a. Within the outer <resume> tag, there is tag <S000>, which contains all the narratives that did not belong to job experiences that have a start-date and an end-date or a distinct duration of time. Nested within the <S000> tag are tags that labeled by duration of time and nested in an ascending order of the value of the duration. These are ‘duration tags’ and have a length that is a duration of time. The duration tags are system-wide predefined to constitute an ascending series of values for duration. These duration tags can be in any unit of time. Again, the values of the data elements of the series are in ascending order with no other pattern. Their selection is established to produce optimal performance. Whether it is a subset or a superset of another phrase within resume 115 a, each experience-related phrase is identifiable as an entity and is stored in XML resume 410. Although the words of an experience-related phrase might overlap with the words of other experience-related phrases, as a separate entity, each experience-related phrase appears once and only once in XML resume 410 of resume 115 a. For each resume 115 a, resume parser program 312 and phrase mapping program 313 store experience-related phrases within a duration tag whose value, among the duration tags in the series, is the largest that is smaller than the maximum possible duration of experience of the experience-related phrase. Again, the maximum possible duration (maximum-total-duration) of experience of an experience-related phrase is the total duration of all the jobs during which the experience-related phrase appeared in resume 115 a. The maximum-total-duration is the maximum duration that can be derived from resume 115 a for the experience-related phrase.

The value of duration tags is an ascending series of numbers each representing a time period. Since resumes traditionally contain job start-dates and end-dates down to a specific day, the value of the duration tags can possibly be in days. In another embodiment, the value of individual duration tags is in a number of seconds, minutes, hours, days, weeks, months, years, or decades. An example is that the value of a duration tag can be five days; two and a half months; and one year, three quarters, and half a month. For all resumes within a single implementation of the resume management and recruitment workflow system 140, the chosen series of values for the duration tags is the same. In another embodiment, a different series can be chosen for each recruiter 120 a or each team 125 as long as they are searching within their exclusive private pool of resumes. One of the factors in establishing the values of the series of the duration tags is performance. For example, smaller values of the duration tags will result in larger consumption of storage space by the XML table 540 and vice versa. Smaller values will create extra work for resume parser program 312 and vice versa. When the values of the duration tags are smaller, resume searching program 315 retrieves a more accurate list of matching candidates and vice versa.

In another embodiment, each experience-related phrase and its maximum-total-duration tag make up an indexed composite key to a table (referred to in this disclosure as the substitute-to-XML-table) that substitutes XML table 540 but likewise points to resume table 550. For each experience-related phrase, the substitute-to-XML-table include additional records that have an indexed composite key comprising the experience-related phrase and each value of the tag series that would have been an XML duration tag and is less than the maximum-total-duration. In other words, the series duration values, which would have been used in the XML duration tags and that are smaller than the maximum-total-duration, are utilized in conjunction with the experience-related phrase to make up composite keys to the substitute-to-XML-table. For each such distinct composite key, there is a record in the substitute-to-XML-table pointing to resume table 550. A search that requires a minimum duration of experience in an experience-related phrase would first locate in the series of values of duration tags the smallest value that is larger than the required minimum duration. Then the experience-related phrase along with the located tag value will make up a search key to the substitute-to-XML-table. Resume 115 a contained in resume table 550 is pointed to by the substitute-to-XML-table record whose composite key is made up of the required experience-related phrase and the located (duration tag) value in XML resume 410. It is to be understood that this single experience-related phrase search scenario is expandable to include more than one experience-related phrase in a Boolean or intuitive layout as per the acceptable input to resume searching program 315.

In one embodiment, the search criteria entered in resume searching program 315 generates a virtual look-up in XML table 540 or substitute-to-XML-table for each experience-related phrase mentioned in the criteria. In another embodiment, the output of the multiple look-ups for the multiple experience-related phrases are combined to result in a list of resumes that are true to the total criteria and are a match to the search or job requirements. In another embodiment, different database management systems handle the prioritization and concurrency of the execution of searches that require a join between multiple sub-output of the same search in differing manners. The utilization of XML to store and retrieve resume information is independent of and has no relation to the utilization of XML by the XML resume library system sponsored by the Open Source software development web site, the HR-XML Consortium, SourceForge.net, or any other implementation that utilizes XML to store resume or career-related data.

XML table 540 also stores the date on which the resume was received or latest updated and refers to this date as the date created. XML table 540 stores this creation date multiple times in individual units of time. The units of time can be seconds, hours, days, months, years, or any fraction, multiple or combination thereof. So, the creation date is a point in time, which is a multiple of a unit of time, so many units away from an origination date of the count. For instance, the origination date could be Jan. 1, 1980 and the creation date could be Mar. 10, 1983. In month units of time, the Mar. 10, 1983 will be 39. The 39 represents 39 months away from Jan. 1, 1980.

XML table 540 also stores the educational degree in nested tags that represent all the degrees lower or equal to the degree earned by candidate 110 a. Within the nest, the field of specialization, the year the degree was earned, and the school from which it was earned are stated.

XML table 540 also stores the salary desired by candidate 110 a. XML table 540 stores the desired salary multiple times in individual dollar units. The dollar units can be in individual dollars or in multiples of dollars. For example, the stored desired salary can be 36,000 individual dollars or equivalently seven five thousand dollars, where individual dollars and five thousand dollars are the dollar units respectively. Resume management and recruitment workflow system 140 rounds the desired salary to the highest multiple of a dollar unit that is smaller than the desired salary.

Resume Table

Resume table 550 retains resume 115 a in its original shape, form and content. Resume table 550 retains an unaltered copy of resume 115 a, as it was received from the sender by resume management and recruitment workflow system 140, whether resume 115 a was electronically mailed, cut-and-paste, uploaded, bulk loaded, or generated by resume maker program 317 for resume management and recruitment workflow system 140. The copy of resume 115 a in resume table 550 gets displayed for the recruiter or other users to view in step 630 and in step 930.

FIG. 6 is a flow diagram of an embodiment of resume management and recruitment workflow system 140 receiving a job requirement from recruiter 120 a or adding a resume from candidate 110 a. Recruiter 120 a initiates the process of adding a job to resume management and recruitment workflow system 140. Recruiter 120 a enters a list of required and alternative experience-related phrases and the minimum duration of experience that is required in each phrase for candidate 110 a (step 610). For each required experience-related phrase in the list, recruiter 120 a may specify a list of alternate experience-related phrases. For example, if recruiter 120 a wishes to consider candidates with a minimum two years of experience in the Java programming language, recruiter 120 a may list alternative skill or experience-related phrases such as one and a half years of experience in C++ or three years of experience in PASCAL. Thus, a search will return any candidate with two years of experience in Java, the required skill or experience-related phrase, one and a half years of experience in C++ (a listed alternative) or three years of experience in PASCAL (another listed alternative). Recruiter 120 a may exclude candidates who meet similarly structured criteria of a different set and/or combination of experience-related phrases. An example would be: two years in Java and either one and a half years in C++ or three years in PASCAL, but not to include those candidates who have two years in brokerage and one year of management or whose Java experience is over five years. In addition, recruiter 120 a may also list some attributes, such as educational level or field of specialization, geographic location, and desired salary, which would be required of candidate 110 a to be a match to the job.

Resume management and recruitment workflow system 140 determines whether recruiter 120 a wants to save the entered job description to resume database 302 (step 615). If recruiter 120 a requests to save the job, resume management and recruitment workflow system 140 stores the entered job information (step 620), as well as all the listed requirements, and matches the requirements for the new job to resume database 302 (step 625). If recruiter 120 a does not request to save the job, resume management and recruitment workflow system 140 performs an instantaneous check of resume database 302 and matches the requirements for the new job to resume database 302. Recruiter 120 a views each resume retrieved by the search performed (step 630). Recruiter 120 a qualifies the matched resumes and presents the qualified resumes to hiring manager 130 a (step 670). Recruiter 120 a documents any interview or hiring as part of a candidate's history, if desired. Note that recruiter 120 a and hiring manager 130 a can be the same and each may be the employer or a representative acting on behalf of the employer.

FIG. 6 also provides an overview of the process of transmitting resume 115 a for candidate 110 a to resume management and recruitment workflow system 140. Candidate 110 a or somebody on behalf of the candidate initiates transmission of resume 115 a to resume management and recruitment workflow system 140. Resume management and recruitment workflow system 140 extracts the candidate's attributes from resume 115 a, as well as the candidate's experience-related phrases and the maximum-total-duration of experience for each experience-related phrase (step 645). Resume management and recruitment workflow system 140 stores resume 115 a in resume table 550 and the extracted information in XML table 540 of resume database 302 (step 650). In addition, resume management and recruitment workflow system 140 stores information on job experiences such as title, company name, department name, location, other job header data, and the job duration in candidate table 510 of resume database 302. Resume management and recruitment workflow system 140 stores the output of resume parser program 312 in candidate table 510 of resume database 302. Again, the output of resume parser program 312 includes each experience-related phrases and the associated maximum-total-duration of experience tag and all the broad phrases of the experience-related phrases and the maximum-total-duration of experience tags of the broad phrases. Resume management and recruitment workflow system 140 matches the newly received resumes to any active jobs listed in resume database 302 (step 655). Again, each matching candidate has a resume that contains the set of experience-related phrases or their narrow terms at a maximum-total-duration of experience that exceeds the required minimum duration of experience for each of the experience-related phrases or their alternatives that are required by the job. Resume management and recruitment workflow system 140 alerts recruiter 120 a if there is a match between the resume and the job posted by recruiter 120 a (step 660). Recruiter 120 a qualifies the matched resumes and presents the qualified resumes to hiring manager 130 a (step 670). Recruiter 120 a may document any interview or hiring activity as part of a candidate's history and job's history, if desired. Note that recruiter 120 a and hiring manager 130 a can be the same person and each may be the employer or a representative acting on behalf of the employer.

FIG. 7 is a flow diagram of an embodiment of resume management and recruitment workflow system 140 displaying a list of jobs, searching through previously entered and stored job descriptions and their specifications, and adding a new job and its description and specification. A recruiter begins using the system by selecting a category for viewing jobs (step 705). A member of a recruitment team (e.g., recruiter 120 b of recruitment team 125) may select to view all the open jobs for every member of the recruitment team (e.g., recruiter 120 b and recruiter 120 c) (step 710). A member of a recruitment team (e.g., recruiter 120 b of recruitment team 125) may select to view all the jobs ever created (i.e., both open and closed jobs) by any member of the recruitment team (e.g., recruiter 120 b, or recruiter 120 c) (step 715). A recruiter (e.g., recruiter 120 a, recruiter 120 b, or recruiter 120 c) may select to view all open jobs posted by the recruiter (step 720). A recruiter (e.g., recruiter 120 a, recruiter 120 b, or recruiter 120 c) may select to view all the jobs ever created (i.e., both open and closed jobs) by the recruiter (step 725). A recruiter (e.g. recruiter 120 a, recruiter 120 b, or recruiter 120 c) may select to view all the closed jobs owned by the recruiter (step 730).

Once the recruiter has made a selection and resume management and recruitment workflow system 140 displays a list of jobs, the user decides whether to filter the jobs by the posting date (step 735). If the recruiter requests to filter the jobs by the posting date (step 740), the jobs are actually filtered and a list is displayed to the recruiter (step 745). If the recruiter does not want to filter the jobs by the posting date (step 745), the unfiltered jobs are displayed in a list to the recruiter. The recruiter has an option (step 750) to either add a new job to resume database 302 (step 755), search for an existing stored job based on specific criteria (step 760), or view a job from the displayed list of jobs (step 770). The recruiter may view a list of candidates who match the job (step 780). Each matching candidate has a resume that contains the required set of experience-related phrases, their alternatives, or the narrow terms of the original experience-related phrases or their alternatives at a maximum-total-duration of experience that exceeds the required minimum duration of experience for each of the experience-related phrases or their alternatives that are required by the job. The recruiter may view the resume of a candidate that matches the displayed job (step 780).

FIG. 8 is a flow diagram of an embodiment of resume management and recruitment workflow system 140 parsing resume 115 a, storing its parsed data in resume database 302 and matching resume 115 a and its candidate 110 a to a stored job, if applicable. Candidate 110 a initiates the posting of a resume. Candidate 110 a selects one method for posting resume 115 a to resume management and recruitment workflow system 140 (step 805). Resume management and recruitment workflow system 140 accommodates candidate 110 a sending the resume as an attachment to an electronic mail message (step 810) or making a digital copy of the resume in another application and pasting the digital copy into user interface program 310 (step 815). Resume management and recruitment workflow system 140 also accommodates candidate 110 a operating user interface program 310 to browse a file directory listing, select a file that includes the resume, and upload the resume to the resume management and recruitment workflow system 140 (step 820). Resume management and recruitment workflow system 140 also accommodates a user uploading at least one resume in a bulk upload (step 825) or, if candidate 110 a does not have a prepared resume, operating resume maker program 317 to author a new resume (step 835).

After candidate 110 a uploads resume 115 a to resume management and recruitment workflow system 140, the process flow shown in FIG. 8 parses the resume (step 840). Steps 840, 850, and 855 represent resume parser program 312 and phrase mapping program 313. Resume management and recruitment workflow system 140 extrapolates attributes for candidate 110 a (step 850). Resume management and recruitment workflow system 140 computes the maximum length of experience (i.e., maximum-total-duration) that each of the experience-related phrases can have and assigns the maximum-total-duration XML tag as an attribute to the experience-related phrase for resume 115 a of candidate 110 a (step 855). An experience-related phrase is any one or more consecutive words that appear in a job assignment description within a resume. All the broad phrases of experience-related phrases are also experience-related phrases.

Resume management and recruitment workflow system 140 stores every experience-related phrase that candidate 110 a lists in resume 115 a, including all broader phrases (step 860) in XML table 540. In XML table 540, resume management and recruitment workflow system 140 writes the experience-related phrase within a duration tag whose value is smaller than the maximum-total-duration of the experience-related phrase and is the largest in a pre-defined series of duration tags. Resume management and recruitment workflow system 140 matches resume 115 a to all active open jobs (step 865). If resume management and recruitment workflow system 140 determines that resume 115 a matches the requirements of an open job (step 870), resume management and recruitment workflow system 140 proceeds to notify recruiter 120 a (step 875). In one embodiment, the notification means is an electronic mail message. However, any method of communication (e.g., telephone, facsimile, or letter carrier) by recruiter 120 a or automatically by resume management and recruitment workflow system 140 that notifies candidate 110 a of the match is sufficient. If resume management and recruitment workflow system 140 does not find a match, the process ends with no further action.

FIG. 9 is a flow diagram of an embodiment of resume management and recruitment workflow system 140 searching resume database 302 for a list of resumes and, therefore, candidates that meet a set of requirements input by recruiter 120 a. One shown candidate at a time, resume management and recruitment workflow system 140 allows recruiter 120 a to view, the attributes, experiences and resumes of all or chosen candidates from the list. Recruiter 120 a initiates the search for resume 115 a that meets a given search criteria.

Recruiter 120 a enters a list of all the skill or experience-related phrases sought in candidate 110 a (step 905). Recruiter 120 a may enter a skill or experience-related phrase required in a candidate by providing an exact description, a representative phrase of it, or any other acronym, skill name or experience-related phrase that may describe or stand for the skill or the experience-related phrase. Recruiter 120 a may enter one or more alternative experience-related phrases that can identify alternates to the previously entered and required experience-related phrase. Each of these alternatives can fully substitute the need for the original phrase in the resume and can, therefore, satisfy the full need of the requirement for the original skill or experience-related phrase. For example, if the original phrase is “Oracle”, recruiter 120 a might be satisfied with a resume that contains “Sybase” or “Informix” as possible alternatives. Note that this searchable alternative to the experience-related phrase in resume management and recruitment workflow system 140 should not be confused with the phrase mapping feature of the resume management and recruitment workflow system 140. At search time, narrow phrases of the required experience-related phrase or its stated alternatives by recruiter 120 a are implicit alternatives in resume 115 a to the required experience-related phrase or its stated alternatives by recruiter 120 a. Thus, the narrow phrases are transparent to recruiter 120 a. Resume management and recruiter workflow system 140 will retrieve resumes that contain the narrow phrases of the required experience-related phrases or the narrow phrases of the alternatives stated by recruiter 120 a as matching resumes. The term ‘implicit’ is utilized because the broad phrase might not exist in resume 115 a. When resume 115 a arrives, resume management and recruitment workflow system 140 maps the narrow phrase to its broad phrases and additionally inserts the broad phrases in XML table 540. These broad phrases might be the phrases that comprise all or part of the search criteria. Although these broad phrases might not have existed in resume 115 a or in all the resume jobs in which they need to exist, they caused the match to occur and therefore the narrow phrases had an indirect implicit effect on satisfying the match.

Furthermore, recruiter 120 a may provide a required minimum length of experience for any of the skill or experience-related phrases that comprise the search, whether the phrases are those originally required or their alternatives as stated by recruiter 120 a. To fulfill the requirement of recruiter 120 a, the required minimum length of experience of the experience-related phrase or its stated alternatives has implications on the requirement of the narrow phrase, referred to in the previous paragraph, whether the narrow phrase is combined with its required broad phrase or not. Again, note that the mapping of the narrow phrase to the broader required phrase took place when the resume was received by resume management and recruiter workflow system 140 and not at search time. Resume parser program 312 and phrase mapping program 313 had already mapped the narrow phrase, which appeared in the original incoming resume 115 a of candidate 110 a, to all its possible broad phrases among which happened to be the required phrase or its alternatives. These broad phrases were stored in XML resume 410 as experience-related phrases and their maximum-total-duration is at least the maximum-total-duration of the narrow phrase from which they were derived. Thus, the value of duration tag of the broad phrases is at least the value of the duration tag of the narrow phrase from which they were derived. For example, a resume might have two jobs; one three-year job containing Java and another four-year job containing JSP. Let's say that mapping table 530 has Java as a broad phrase of JSP. Assuming that JSP does not appear in the three-year job, the maximum-total-duration of JSP is four years, while Java is seven years. Assuming that the duration tag series is small enough, a search that requires a minimum of five years of Java will be satisfied thanks to the JSP narrow phrase that contributed an additional four years to the Java three years mentioned experience to a total of seven years. That is, at search time, the narrow phrases contributed to the expansion of the value of the duration of the broad phrase and therefore, enabled the broad phrase to meet the requirement of recruiter 120 a.

Resume management and recruitment workflow system 140 determines whether recruiter 120 a entered the search criteria in the intuitive layout or as a Boolean expression (step 910). If recruiter 120 a entered the search data in an intuitive layout, the process converts the search data to a Boolean expression (step 915) and displays both the intuitive layout and the Boolean expression to recruiter 120 a. If recruiter 120 a entered the search data as a Boolean expression, the process converts the search data to an intuitive layout (step 920) and displays both the Boolean expression and the intuitive layout to recruiter 120 a. Thus, whether the user chooses the intuitive layout or the Boolean expression as the method of data entry, resume management and recruitment workflow system 140 converts the search data to the other method of data entry and displays both forms of the search expression to recruiter 120 a.

In the intuitive layout form of data entry, recruiter 120 a enters a list of phrases required for a job opening into resume management and recruitment workflow system 140. Resume management and recruitment workflow system 140 combines the phrases that comprise the list using a Boolean “and” between each phrase. Since each phrase may also include alternatives, resume management and recruitment workflow system 140 combines the alternatives using a Boolean “or” between each alternative. The resulting expression is the intersection (i.e., Boolean “and”) of a number of unions (i.e., Boolean “or”) of phrases. The expression “(A or B) and (C or D or E)” is an example that might result from the intuitive layout of data entry of the search criteria.

Additionally, note that this representation of an intersection of a number of unions of phrases is a representation that can cover the union of a number of intersections of phrases. For example, if the requirement is for the union of the intersection of phrases: “(A and B) or (C and D and E)”, then the requirement is equivalent to the following intersection of unions acceptable as an input to the intuitive layout of data entry for the criteria: “(A or C) and (A or D) and (A or E) and (B or C) and (B or D) and (B or E)”. It is to be understood that “(A and B) or (C and D and E)” is equivalent to “(A or C) and (A or D) and (A or E) and (B or C) and (B or D) and (B or E)”. This conversion is important because the intuitive layout form of data entry accepts a required list of and'ed phrases each of which is or'ed with a number of alternatives. Or'ing of lists of and'ed phrases will be converted to and'ing of or'ed phrases. Note that the intuitive layout form of data entry referred to here, which is and'ing the or's, is closer to the way people select a meal from a multiple course menu. We select one appetizer from a list of or'ed few, one main course from a list of or'ed few, one drink from a list of or'ed few, one desert from a list of few, and so on. Then, we join (and) the selected list of items, skipping some at times. For example, we might pass on the drink. The selection from this food menu is the and'ing of or'ed items. In fast food chains, we select meals, each of which, make up an and'ing of items. We can select one or more of the meals through a choice from an or'ing of the and's. Again, as stated above, both methods of setting up a search criteria can be represented or converted to the intuitive layout of and'ing multiple or's.

Since resume management and recruitment workflow system 140 accommodates the intersection of multiple unions and, thereby the union of multiple intersections along with the negation or exclusion of a similar intersection or union, the search covers all possible search criteria that a job opening might require of an individual. Required complex nested Boolean phrases can be easily broken down to the intersection of unions or the union of intersections and therefore can all be covered by the intuitive layout. Purging the output list of resumes from rejected resumes, which are true to another combination of phrases that adhere to another Boolean expression or input through the intuitive layout, accommodates the possible negation in a Boolean expression. In other words, the output of a list of required skill or experience-related phrases and their alternatives can be cut down by the resumes that adhere to some unwanted similar combination of phrases.

The intuitive approach for entering the search improves the usability of resume management and recruitment workflow system 140 because recruiter 120 a does not need to type a Boolean expression. On the other hand, the Boolean expression approach for entering the search improves the flexibility of resume management and recruitment workflow system 140. Whether recruiter 120 a enters a list of required skill or experience-related phrases and alternatives or enters a Boolean statement, resume management and recruitment workflow system 140 converts one form to the other and displays both forms to the user. Resume management and recruitment workflow system 140 also provides the user with interface tips and feedback on obvious errors in data entry. Additionally, resume management and recruitment workflow system 140 provides spelling checks for phrases searched and for notes on the candidates.

Resume management and recruitment workflow system 140 displays a list of candidates meeting the criteria entered by recruiter 120 a (step 925). The system provides a split-screen view that displays the candidate attributes in one portion and the individual resume in the other portion (step 930). The resumes are displayed for each candidate that recruiter 120 a selects to view by selecting one candidate's name from the list of the candidates displayed by resume management and recruitment workflow system 140. Recruiter 120 a chooses which resume to view from the list of the candidates that meet the search criteria (step 940).

Resume management and recruitment workflow system 140 determines whether recruiter 120 a wants to view additional resumes for other possible candidates (step 945). If recruiter 120 a decides to view additional resumes, the process flow returns to step 930 otherwise, the process flow ends.

According to one embodiment, resume management and recruitment workflow system 140 incrementally displays the output of a search for resumes that fit the search criteria. Resume management and recruitment workflow system 140 retrieves and displays the outcome of incremental searches from the resume database 302. The initial batch of resumes displayed will begin with the most recently received or updated resume and proceed backward for a period of time. Subsequent batches of resumes retrieved by resume management and recruitment workflow system 140 will proceed backward further in time. Each search performed by resume management and recruitment workflow system 140 increases the period of time that the search covers by going back further in time. Thus, the backward incremental search will have longer leaps into the past as the incremental search continues. Each increment will start where the other increment ended. The search is complete either following an exhaustive search of resume database 302 or the attainment of specified number of resumes that meet the needs of recruiter 120 a.

FIG. 10 is a data flow diagram of an embodiment of resume management and recruitment workflow system 140 illustrating an exemplary job search. Candidate 110 a (shown as box 1000) populates resume database 302 by posting a resume to resume management and recruitment workflow system 140. Recruiter 120 a (shown as box 1005) stores a description for a job in resume database 302. Recruiter 1005 also initiates a database search 1010 for matched candidates 1015 by sending the job requirements. The search sends a query to resume database 302 and receives a result set. Resume management and recruitment workflow system 140 stores the result set as matched candidates 1015. Resume management and recruitment workflow system 140 accesses matched candidates 1015 to display the results to recruiter 120 a. When recruiter 120 a is interested in a candidate, recruiter 120 a retrieves the resume from matched candidates 1015.

FIG. 11 is a data flow diagram of an embodiment of resume management and recruitment workflow system 140 illustrating the transmission of a resume from candidate 110 a to resume database 302. Initially, candidate 110 a (shown in box 1100) provides a resume to resume management and recruitment workflow system 140. Candidate 1100 may input the resume to resume management and recruitment workflow system 140 using electronic mail 1105, cut and paste 1110, upload 1115, bulk load 1120, or use resume maker 1125. Resume management and recruitment workflow system 140 receives the resume in word converter 1130. Word converter 1130 converts the resume into common document formats such as ASCII text, HTML, Rich Text Format (RTF), or the like. Word converter 1130 sends the text form of the resume to the resume parser 1140. Word converter 1130 also sends RTF and the HTML versions of the resume to the traffic controller resume servlet 1150. Resume parser 1140 parses the resume in text format to search for any and all information relating to a candidate work experience, generates the candidate's attributes, and forwards the data to the traffic controller resume servlet 1150.

The traffic-controller resume servlet 1150 forwards all the gathered information in text format to work experience converter and XML generator 1160. Traffic-controller resume servlet 1150 also sends the candidate's attributes to resume database 302 for storage. As discussed above, recruiters ultimately use resume database 302 to search for candidates that may satisfy the recruiter's search criteria, or by candidates to search for desired job openings.

In one embodiment, when matching incoming resumes to job requirements resume management and recruitment workflow system 140 utilizes a search mechanism that reverses the operation of a SELECT statement. The search retrieves all the jobs whose requirements are met by the incoming resume (i.e., the executed SELECT statement retrieves the incoming resume), among other resumes, in its output. This search is the reverse of a search for candidates who meet a job's criteria (i.e., the search is the reverse of a SELECT statement that results in a list of candidates that fit the job and are true to the SELECT statement). Resume management and recruitment workflow system 140 matches the incoming resume to the active jobs by implicitly executing all SELECT statements of all open and active jobs to determine which jobs would have picked up the candidate as a match.

In accordance with one embodiment of the present invention, events entered by recruiter 120 a as events along with the various activities of presenting resumes to clients, scheduling interviews and scheduling hires are recorded in a private consolidated calendar for each of the recruiters.

In accordance with one embodiment of the present invention, resume management and recruitment workflow system 140 contains private, semi-private, and public resumes. Private ownership may belong to a recruitment team. Some resumes may belong to individual recruitment teams. Other resumes may still be private, but shared among several recruitment teams. The majority of the resumes are public resumes. Recruitment team members will have access to both the team's private resumes and public resumes and may share notes or activities on any resume or candidate among their individual team members. Team members may not share notes and activities across team boundaries even if the resume is a public resume. Only the owners of a job requirement may be able to modify a job.

FIGS. 12A through 12M are exemplary screen images from an implementation of resume management and recruitment workflow system 140. FIG. 12A illustrates an exemplary screen image depicting the options of what a recruiter may view in respect to the job vacancies for which the recruiter or the recruiter's company is responsible. FIG. 12B illustrates an exemplary screen image depicting other options for searching for different jobs by recruiters using selected criteria. FIG. 12C illustrates an exemplary screen image for allowing recruiters to add a new job listing. FIG. 12D illustrates an exemplary screen image for viewing a job from a displayed list of jobs. The recruiter may click on a link to “View Matched Candidates” to display the candidates that have been matched to this job based on the required skill or experience-related phrases and length of time entered by the recruiter. FIG. 12E illustrates an exemplary screen image for viewing the matched candidate screen where the most recent candidates that fit the required skill or experience-related phrases appear. The recruiter is able to click and check off the candidates they have viewed in addition to being able to view which candidates have notes in the system on them already and who have been previously submitted to a job.

FIG. 12F illustrates an exemplary screen image for allowing the different methods of posting the resume to resume management and recruitment workflow system 140. As previously discussed, the options available to job candidates are to upload, e-mail, cut and paste, or use the resume maker. From there, resume management and recruitment workflow system 140 parses the resume and the process continues through the resume processing flow internally.

FIG. 12G illustrates an exemplary screen image for parsing the resume and creating its attributes. The system displays the extrapolated information in the top left-hand corner. The extrapolated information includes name, address, e-mail, etc. Then, resume management and recruitment workflow system 140 extrapolates the candidate's work experience and skill or experience-related phrases and displays the result in the work experience field.

FIG. 12H illustrates an exemplary screen image after entering the resume, parsing the resume, and matching the resume to all open jobs that match the skill or experience-related phrases. Subsequently, resume management and recruitment workflow system 140 notifies the recruiter and the candidate names appear in the view matched candidates screen for that job.

FIG. 12I illustrates an exemplary screen image for initiating a search for candidates from the resume database 302. FIG. 12J illustrates an exemplary screen image showing the capability to perform a search within a search by excluding specific candidates to narrow down the results more specifically. FIG. 12K illustrates an exemplary screen image for allowing recruiters to add skill or experience-related phrases and their alternatives in addition to length of experience required. From the screen, two methods of entry are available for the user, an intuitive layout (the top sections of entered skill or experience-related phrases in FIG. 12K) and a Boolean expression (the bottom box with the text and parentheses in FIG. 12K). Regardless of the method chosen, resume management and recruitment workflow system 140 automatically converts the data entered to the other method in the appropriate field.

FIG. 12L illustrates an exemplary screen image for displaying the results of the search incrementally. When clicking on the “Next” button and the “>>” to the right of the “Next” button, additional results are displayed until the search has been exhausted.

FIG. 12M illustrates an exemplary split screen image. The split screen allows a recruiter to view the multiple resumes of a candidate, the candidate's attributes, any notes written by any recruiter on the recruiter's team, candidate activity by members of the team, in addition to the search results including shaded candidates that have been viewed by the recruiter.

In another embodiment, resume management and recruitment workflow system 140 offers electronic mail capability from the site. A user can send individual e-mail messages using the e-mail address hyperlink from the candidate information screen. In addition, the user can send multiple e-mail messages within a very short time period. In another embodiment, resume management and recruitment workflow system 140 includes tool tips in the user interface. In another embodiment, resume management and recruitment workflow system 140 consolidates events into a calendar as well as a reporting form for the user to view different activities. In another embodiment, resume management and recruitment workflow system 140 provides the ability to find a candidate using the candidate's name, electronic mail address, postal address, phone number, and the like. In another embodiment, as the user views the candidate or the job, the system shades the list of candidates and jobs that result from a search and have been viewed. Thus, the screen display will indicate those candidates or jobs reviewed by the user. In another embodiment, resume management and recruitment workflow system 140 allows the user to open and print a resume from the candidate screen and re-format it or save it wherever the user wants. In another embodiment, resume management and recruitment workflow system 140 discerns that multiple resumes sharing the same electronic mail address belong to the same candidate attributes. Resume management and recruitment workflow system 140 resolves the latest most relevant data and presents that latest attributes to the user. In another embodiment, resume management and recruitment workflow system 140 allows the user to use the full resume as a search platform by selecting zero years or specifying no years for the phrases in the search criteria. In another embodiment, resume management and recruitment workflow system 140 utilizes a state, area code, education, and desired salary filtering for a search for candidates.

In another embodiment, resume management and recruitment workflow system 140 provides access to resume database 302 in a non-traditional employer-employee relationship. Exemplary non-traditional employer-employee relationships include internal placement of current employees to new tasks or projects, and coordination of the placement of current employees among the organizations that make-up a distributed network of organizations such as branches of the Federal government.

Although the disclosed embodiments describe a fully functioning resume management and recruitment workflow system and method, it is to be understood that other equivalent embodiments exist. Since numerous modifications and variations will occur to those who review this disclosure, the resume management and recruitment workflow system and method is not limited to the exact construction and operation illustrated and disclosed. Accordingly, this disclosure intends all suitable modifications and equivalents to fall within the scope of the claims. 

I claim:
 1. A method comprising: receiving, at a computing device, a plurality of resumes in an electronic format, each received resume comprising portions of electronic data comprising phrases of text related to an attribute of a respective resume; parsing, via the computing device, each received electronic resume and the portions of electronic data comprised therein, and identifying tags associated with the phrases of text for each attribute; determining, via the computing device, based on said parsing and identifying, an experience range for each attribute in the received electronic resumes, said determination comprising identifying a start time and an end time for each attribute based on the identified tags of each attribute; computing, via the computing device, a term of experience for each attribute based on each attribute's start time and end time; generating, via the computing device, a duration tag for each attribute, each duration tag comprising information indicating said term of experience of an attribute; creating, via the computing device, nesting data for each resume, said nesting data comprising the duration tags for each resume in ascending order of duration such that, for each resume, the attributes with longer terms of experience have a higher value than other attributes with less terms of experience; storing, via the computing device, said created nesting data for each resume in a resume database; receiving, via the computing device, a resume search request from a user comprising a job description, said job description comprising at least one job requirement corresponding to a required attribute and a required term of experience; searching, via the computing device, in response to said resume search request, said resume database, said searching comprising analyzing the nesting data for each resume based on said job description, and determining an attribute from a resume satisfying the job requirement; identifying, via the computing device, the corresponding electronic resume of the determined attribute; and communicating, via the computing device, said identified electronic resume to a device of said requesting user.
 2. The method of claim 1, further comprising: extracting data from each resume corresponding to each attribute.
 3. The method of claim 2, further comprising: storing, in said resume database, said extracted data in association with each resume's nesting data.
 4. The method of claim 1, further comprising: storing each resume as a private resume, wherein the resume database is accessible by a group of users, and the private resume is accessible by only permitted users of said group, wherein said nesting data for each resume is private.
 5. The method of claim 1, further comprising: analyzing the text associated each attribute, and based on said analysis, determining a context of each attribute; and storing, in association with said nesting data for each resume, said context.
 6. The method of claim 5, wherein said search for said resume is further based on said context.
 7. The method of claim 5, wherein the text of each resume that surrounds each attribute is at least one of a summary narrative, an experience narrative, and a closing narrative.
 8. The method of claim 1, wherein the duration of time is an integer number of a unit of time, and wherein the unit of time includes at least one of seconds, minutes, hours, days, weeks, months, years, and decades.
 9. The method of claim 1, further comprising: storing said resume search request and said job description included therein in said resume database.
 10. A non-transitory computer-readable storage medium tangibly encoded with computer-executable instructions, that when executed by a processor associated with a computing device, causes the computer to perform a method comprising: receiving, at the computing device, a plurality of resumes in an electronic format, each received resume comprising portions of electronic data comprising phrases of text related to an attribute of a respective resume; parsing, via the computing device, each received electronic resume and the portions of electronic data comprised therein, and identifying tags associated with the phrases of text for each attribute; determining, via the computing device, based on said parsing and identifying, an experience range for each attribute in the received electronic resumes, said determination comprising identifying a start time and an end time for each attribute based on the identified tags of each attribute; computing, via the computing device, a term of experience for each attribute based on each attribute's start time and end time; generating, via the computing device, a duration tag for each attribute, each duration tag comprising information indicating said term of experience of an attribute; creating, via the computing device, nesting data for each resume, said nesting data comprising the duration tags for each resume in ascending order of duration such that, for each resume, the attributes with longer terms of experience have a higher value than other attributes with less terms of experience; storing, via the computing device, said created nesting data for each resume in a resume database; receiving, via the computing device, a resume search request from a user comprising a job description, said job description comprising at least one job requirement corresponding to a required attribute and a required term of experience; searching, via the computing device, in response to said resume search request, said resume database, said searching comprising analyzing the nesting data for each resume based on said job description, and determining an attribute from a resume satisfying the job requirement; identifying, via the computing device, the corresponding electronic resume of the determined attribute; and communicating, via the computing device, said identified electronic resume to a device of said requesting user.
 11. The non-transitory computer-readable storage medium of claim 10, further comprising: extracting data from each resume corresponding to each attribute.
 12. The non-transitory computer-readable storage medium of claim 11, further comprising: storing, in said resume database, said extracted data in association with each resume's nesting data.
 13. The non-transitory computer-readable storage medium of claim 10, further comprising: storing each resume as a private resume, wherein the resume database is accessible by a group of users, and the private resume is accessible by only permitted users of said group, wherein said nesting data for each resume is private.
 14. The non-transitory computer-readable storage medium of claim 10, further comprising: analyzing the text associated each attribute, and based on said analysis, determining a context of each attribute; and storing, in association with said nesting data for each resume, said context.
 15. The non-transitory computer-readable storage medium of claim 14, wherein said search for said resume is further based on said context.
 16. The non-transitory computer-readable storage medium of claim 14, wherein the text of each resume that surrounds each attribute is at least one of a summary narrative, an experience narrative, and a closing narrative.
 17. The non-transitory computer-readable storage medium of claim 10, wherein the duration of time is an integer number of a unit of time, and wherein the unit of time includes at least one of seconds, minutes, hours, days, weeks, months, years, and decades.
 18. The non-transitory computer-readable storage medium of claim 10, further comprising: storing said resume search request and said job description included therein in said resume database.
 19. A computing device comprising: a processor disposed in communication with a memory device; and the memory device resident on the computing device tangibly storing thereon program logic for execution by the processor, the program logic comprising: logic executed by the processor for receiving, at the computing device, a plurality of resumes in an electronic format, each received resume comprising portions of electronic data comprising phrases of text related to an attribute of a respective resume; logic executed by the processor for parsing, via the computing device, each received electronic resume and the portions of electronic data comprised therein, and identifying tags associated with the phrases of text for each attribute; logic executed by the processor for determining, via the computing device, based on said parsing and identifying, an experience range for each attribute in the received electronic resumes, said determination comprising identifying a start time and an end time for each attribute based on the identified tags of each attribute; logic executed by the processor for computing, via the computing device, a term of experience for each attribute based on each attribute's start time and end time; logic executed by the processor for generating, via the computing device, a duration tag for each attribute, each duration tag comprising information indicating said term of experience of an attribute; logic executed by the processor for creating, via the computing device, nesting data for each resume, said nesting data comprising the duration tags for each resume in ascending order of duration such that, for each resume, the attributes with longer terms of experience have a higher value than other attributes with less terms of experience; logic executed by the processor for storing, via the computing device, the created nesting data for each resume in a resume database; logic executed by the processor for receiving, via the computing device, a resume search request from a user comprising a job description, said job description comprising at least one job requirement corresponding to a required attribute and a required term of experience; logic executed by the processor for searching, via the computing device, in response to said resume search request, said resume database, said searching comprising analyzing the nesting data for each resume based on said job description, and determining an attribute from a resume satisfying the job requirement; logic executed by the processor for identifying, via the computing device, the corresponding electronic resume of the determined attribute; and logic executed by the processor for communicating, via the computing device, said identified electronic resume to a device of said requesting user.
 20. The computing device of claim 19, further comprising: logic executed by the processor for analyzing the text associated each attribute, and based on said analysis, determining a context of each attribute; and logic executed by the processor for storing, in association with said nesting data for each resume, said context, wherein said search for said resume is further based on said context. 